Troubleshooting
Local development
What debugging tools are available?
For general debugging tools, you should familiarise yourself with the development tools of the frameworks we use:
To get even more information, you can enable debug mode in nuxt.config.ts.
Deployment
The installation of production dependencies failed. What can I do about this?
By default, the shop uses the latest LTS version of NodeJS. You may experience problems when the LTS version changes, for example because package-lock.json doesn't match when running npm ci. You have two ways of addressing this issue.
You can either pin a more specific Node version. To pin a version, modify .nvmrc.
If you want to stay on the LTS version, carry out the following steps:
# Downloads and switches to latest LTS version, may differ depending on how you manage your Node versions
fnm install
# Updates package-lock.json in line with new Node version
npm installNew major versions may require other changes as well. Below you can find a reference of adjustments made in the main repository:
The build failed. How can I tell what went wrong?
The build in PlentyONE uses the standard application script. If you npm run build locally, you should get the same output.
💡 Automatic build checks
We recommend adjusting the CI pipeline to your needs, so that every change you make is checked automatically.