-
-
Notifications
You must be signed in to change notification settings - Fork 430
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why are dev dependencies needed at runtime ? #423
Comments
I've created a repo to show the issue and the "fixes" |
I have also found that I cannot build the production server with |
I think this error only happens with Express server, and it's an issue upstream with Nuxt, on this line |
I'm reopenning this issue. With a fresh
I should be able to install for production and start without problem. Please keep a clean package.json 🙏 edit: it's |
Bumping this ^. I had to move a few devDependencies to dependencies in order to get nuxt to build with typescript - so not sure if this is outside the remit of the nuxt project (and more to do with typescript), or even just an issue with Vue itself... |
@chrismooreproductions You need at least |
moved @nuxtjs/eslint-module, @nuxtjs/stylelint-module, and @nuxtjs/vuetify from devDeps to dependencies based upon this github issue- nuxt/create-nuxt-app#423 still trying to deploy to heroku attempt #4
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
Error: Cannot find module 'vuetify/es5/util/colors'
=> solved by moving
@nuxtjs/vuetify
to dependenciesError: Cannot find module '@nuxtjs/eslint-module'
=> solved by moving
@nuxtjs/eslint-module
to dependenciesError: Cannot find module '@nuxtjs/stylelint-module'
=> solved by moving
@nuxtjs/stylelint-module
to dependenciesBut those are bad fixes, those should stay in dev dependencies.
You can reproduce the error with the following steps :
the options used for create-nuxt-app :
The text was updated successfully, but these errors were encountered: