why are dev dependencies needed at runtime ?

I’ve created a fresh new project today with npx create-nuxt-app xxx

It was impossible to deploy it to heroku. (It builded correctly but crashed on server start)

Multiple errors were thrown one after the other

1. Error: Cannot find module 'vuetify/es5/util/colors' => solved by moving @nuxtjs/vuetify to dependencies
2. Error: Cannot find module '@nuxtjs/eslint-module' => solved by moving @nuxtjs/eslint-module to dependencies
3. Error: Cannot find module '@nuxtjs/stylelint-module' => solved by moving @nuxtjs/stylelint-module to dependencies

But those are bad fixes, those should stay in dev dependencies.

You can reproduce the error with the following steps :

npm install
npm run build
npm prune --production
npm run start

the options used for create-nuxt-app :

• npm
• Vuetify.js
• Express
• with all nuxt modules (axios, PWA support, dotenv)
• with all linting tools (ESLint, Prettier, Lint staged files, StyleLint)
• Jest
• Universal
• with jsconfig.json

[pi0]

@chrismooreproductions You need at least nuxt-start and typescript-runtime in dependencies. This is current nuxt2 limitation (we are working on new server engine that allows zero dependency deployments)

[existe-deja]

I’m reopenning this issue. With a fresh yarn create nuxt-app and yarn install --production I get this error:

ERROR in ./.nuxt/client.js
Module not found: Error: Can't resolve 'regenerator-runtime/runtime'
 @ ./.nuxt/client.js 24:0-37
 @ multi ./node_modules/@nuxt/components/lib/installComponents.js ./.nuxt/client.js

I should be able to install for production and start without problem. Please keep a clean package.json 🙏

edit: it’s vue-jest package who needs to be installed in production mode.