webpack / webpack/webpack-bundle-analyzer
Symlinks expand paths of node_modules
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 12.7k
- Forks
- 514
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 4
Description
Issue description
When this is used in an environment where node_modules packages are symlinked (via lerna, @microsoft/rush, npm link) the locations to npm modules are expanded such that it makes things hard to parse. Basically half of the tree map is dedicated to resolving the node_modules folder:
Would there be any way to fix this such that I can provide "filters" that would alias a folder to say blank string, to remove the extraneous path? Any suggestions, other than to avoid symlinking?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the bundle analyzer output with node_modules packages symlinked through lerna, @microsoft/rush, or npm link. Trace where symlinked module paths are expanded and review the existing discussion about filters or aliases. Done means the treemap no longer shows the extraneous resolved path while preserving useful module locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100