Reputation: 30292
I have an ASP.NET Core 1.0 app with an npm_modules folder in it. Each NPM module brings its own dependencies into its folder -- of course each dependency repeats this behavior and we end up with a gazillion levels of subfolders which create a problem on Windows when publishing the app -- the infamous path too long error.
I understand that the new version of NPM uses a flat folder approach. How do I fix this issue on my existing ASP.NET Core app which still has folders within folders for package dependencies?
Upvotes: 0
Views: 913
Reputation: 19428
Simply delete the node_modules
folder in your current project directory and then do an npm install
. This will download all of your package dependencies again while using the new flattened dependency structure of NPM v3.
Upvotes: 1