Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Should it be in buildModules and devDependency?

See original GitHub issue

Shouldn’t documentation state that it should be added in buildModules (or devModules) rather than modules? And shouldn’t it state that this is devDependency then? As far as I can see it only affects building.

Issue Analytics

State:
Created 4 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

2reactions

manniLcommented, Oct 8, 2019

@rchl

Some people use devDeps only for linters + testing utils and put “the rest” (so deps needed at build and at run time) in deps.

Others use devDeps for everything build-related and deps only for runtime builds.

1reaction

curtisbeltcommented, Mar 6, 2020

@simplenotezy hey there, devModules is actually deprecated in favor of buildModules, and you can indeed add it there. The benefit is that buildModules are are not loaded in nuxt start.

Top Results From Across the Web

Do npm dependencies and devDependencies effect your ...

A definitive guide on the differences between you dev dependencies and regular dependencies in your package.json file and how they effect ...

Is this a dependency or devDependency? - With Blue Ink

The reason is that when someone installs your package from NPM, they will install all of its dependencies, but not the devDependencies.

npm install --production should ignore devDependencies in ...

We deploy our app to Heroku which runs an npm install --production . We have a shrinkwrap file in there that is generated...

The modules Property - Nuxt

Instead of adding to modules inside nuxt.config.js , use buildModules; Instead of adding to dependencies inside package.json , use devDependencies ( yarn ...

Build Nuxt.js on production required devDependences

HINT: During build step, for npm/yarn, NODE_ENV=production or --production should NOT be used." But it doesn't make sense because yarn install ...