Why does the npm package I created have a node_modules folder in it when installing it as dependency for another module?

Question

I just published my first npm package. When I install the package as dependency in my project, I open the project folder in node_modules and see that it also has a node_modules folder with one package, history in the folder. I don't have any regular dependencies for my project, only devDependencies so I don't understand why this is happening? You can see my package.json file and try installing the module from the github page here https://github.com/danielyaa5/react-contextulize

Community · Accepted Answer · 2017-05-23 10:32:59Z

1

Running npm install will install devDependencies under many circumstances.

Try explicitly installing in production mode:

npm install --only=production

Here is a related answer with more info.

edited May 23, 2017 at 10:32

CommunityBot

11 silver badge

answered Nov 24, 2016 at 23:24

Steven Schobert

4,2793 gold badges27 silver badges34 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Daniel Kobe Over a year ago

This doesn't make any sense to me though, there must be another way where I don't have to tell my users to install it like this?

Steven Schobert Over a year ago

You shouldn't need to tell your users anything. In production systems where NODE_ENV=production is set, the devDependencies will be skipped.

Collectives™ on Stack Overflow

Why does the npm package I created have a node_modules folder in it when installing it as dependency for another module?

1 Answer 1

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related