enhanced-resolve
enhanced-resolve copied to clipboard
webpack
Offers an async require.resolve function. It's highly configurable.
It looks as though attempts to resolve external modules got jammed somewhere. Did I forget something? Should I pass something extra? Is it a deliberate deprecation? ## Steps taken Run...
I didn't find any documentation where I can see what plugins are available and what these plugins are achieve. Did I overlooked something?
I've been running lots of profiles to find the bottlenecks in our webpack build. Probably the biggest bottleneck right now is resolving requests. To highlight this, I've created a simple...
fixes #356 i need some help with the overloads here i think. you can see the strong types now mean a bunch of tests need to cast things too... im...
Currently many of the exported types are `any` or very weakly typed. It would be great if these types could be properly populated via the jsdoc. For example, the various...
Let’s say we have a TypeScript mono repo with one package that depends on another. The actual TypeScript configuration is left out, because it’s not needed for this example. `webpack.config.js`:...
I am trying to get the enhanced resolver to work with a TypeScript self-reference, both via package.json `exports` and `imports`. When TypeScript looks up modules it deviates from the Node...
Latest v5.16.0 breaks with `lstat` error when using virtual modules: ``` ERROR in ../../../../derby-webpack-virtual-fs/app-views/ sync ^\.\/.*__views$ ENOENT: no such file or directory, lstat '/derby-webpack-virtual-fs' caused by plugins in ContextModule.resolveDependencies Error:...
### What problem does this feature solve? [pnpm](https://pnpm.io/faq#why-does-my-node_modules-folder-use-disk-space-if-packages-are-stored-in-a-global-store) creates hard links from the global store to the project's node_modules folders. For example, imagine you have the following directory structure: `packages/a`...
I implemented general logic for resolving win32 relative paths in library. It's hard to say what else to cover with tests because it's hard to fully mock Node.js's path module...
