[BUG] Application roots without node_modules on disk are missed for versions inference.
See original GitHub issueIn a Next JS app with a custom webpack config, inpectpack prints the following after build, without the information about the actual bundles:
It is a Next v8.0.1 app, running on node v10.8.0 and Webpack 4.29.0.
Relevant part of next.config.js
is:
{
// ...
webpack: (config, opts) =>{
// ...
// Check for duplicate code from dependencies
if (!isServer) {
config.plugins.push(
new DuplicatesPlugin({ verbose: true, })
);
}
return config
},
}
Any insight would be appreciated
Issue Analytics
- State:
- Created 5 years ago
- Comments:36 (22 by maintainers)
Top Results From Across the Web
Where does npm install packages? - Stack Overflow
npm root -g will show the global installation root regardless of current working directory.
Read more >Why the Hell Would I Use Node.js? A Case-by-case Tutorial
Node.js can solve I/O scaling, but was not created to compute scaling problems. Learn why and when to use Node.js in this case-by-case...
Read more >Understanding dependency management with Node Modules
Some common issues I have seen developers face with node modules are often related to a lack of understanding of how version control...
Read more >Troubleshoot instances with failed status checks
One or more of the following conditions can cause this problem: Missing ramdisk. Missing correct modules from ramdisk. Amazon EBS root volume not...
Read more >Manage npm packages - Visual Studio (Windows)
npm expects the node_modules folder and package.json in the project root. If your app's folder structure is different, you should modify ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Cool! For verbose, I think I just was confused by the manual editing of the report output (and I’ve got a ticket #109 to collapse large amounts of dependency graphs for easier reading in the future). Here’s what I see and I’m guessing that matches up with you:
OK, now updated… I think I’ve got everything correctly matched up with what the simple duplicates report has.
side note: It is fascinating to see what all the
fela
-monorepo released stuff ends up with dependency-wise, but looks like modulo a few duplicates, the lerna package release keeps things pinned so we have a ton of logical dependencies from the abstract dependency tree, but only a handful of actual on-disk installations…