asset/resource builds outside of dist when [pathname] contains references to hoisted node_modules
See original GitHub issueBug report
What is the current behavior?
Files located in hoisted node_modules of a workspace and loaded as asset/resource
are built outside of dist. This differs from what file-loader
does
If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/dreyks/asset-resource-bug
What is the expected behavior?
All built files should end up inside the dist folder no matter where they are located on the fs
Other relevant information: webpack version: webpack@5.56.0 Node.js version: v14.13.1 Operating System: MacOS Additional tools:
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:22 (13 by maintainers)
Top Results From Across the Web
Webpack can't resolve asset/resource? - Stack Overflow
So it looks like webpack doesn't find it's own built in package ? The doc s quite clear about t being built in...
Read more >How to transpile ES modules with webpack and Node.js
Learn how webpack interacts with and supports ES modules in this deep dive tutorial on transpilation in Node.js.
Read more >API - ESBuild
#Build API. The build API call operates on one or more files in the file system. This allows the files to reference each...
Read more >CopyWebpackPlugin | webpack
Copies individual files or entire directories, which already exist, to the build directory. Getting Started. To begin, you'll need to install copy-webpack- ...
Read more >Dependency resolution - Parcel
As Parcel builds your source code, it discovers dependencies, ... Parcel includes shims for many builtin Node.js modules, e.g. path and url ....
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
@glen-84 Yeah, we should do it, sometimes developers are lazy 😄
yes, there are some breaking changes between asset modules and
file-loader