Comments (5)
Is this because the contents of the cwd of the build are not the same as the contents of the cwd of the runtime? If so, perhaps set the cwd
option to point to the correct folder? The package.json should be emitted strictly speaking as that's what the asset emitter does.
We could possibly have a cwd: false
option to disable cwd-based emissions.
from webpack-asset-relocator-loader.
Thanks you for the information about cwd: false
. That is exactly what i want.
IMHO, process.cwd()
should be not treated as static in most cases, while static is a feature. i.e. cwd: false
as default.
from webpack-asset-relocator-loader.
I'm open to switching the default.
from webpack-asset-relocator-loader.
IMHO, process.cwd() should be not treated as static in most cases
I think I agree. I am using ncc
in the context of CI/CD (Github Actions), and I need to be able to compile scripts locally and run them on various remote machines. But if I include a dependency that uses process.cwd
, then the scripts I compile locally won't work on the remote runners, because they'll include filepaths on my local machine.
from webpack-asset-relocator-loader.
@roryabraham the safe route here is always to set the cwd
option. A PR to improve the default would be welcome too.
from webpack-asset-relocator-loader.
Related Issues (20)
- Support for symlinks HOT 4
- Running in webpack watch mode doesn't work after a recompile. HOT 4
- Errors out when options isn't specified HOT 1
- With node-loader or awesome-node-loader
- Invalid dependencies have been reported by plugins or loaders for this module. All reported dependencies need to be absolute paths. HOT 1
- Inconsitant handling of path seperators resulting in generateWildcardRequire generating invalid conditions
- Does not work with Electron Forge and `serialport` v10 HOT 2
- [Windows] Path parts in strings replaced with undefined HOT 7
- Yarn berry pnp support HOT 2
- Module build Failed
- Output directory structure for native modules for Electron - any risks here?
- Nextjs native module different behavior in prod mode HOT 6
- Module not found: Error: Can't resolve '@vercel/webpack-asset-relocator-loader' HOT 2
- Better esm support HOT 2
- Binary relocation not working for bindings and node-pre-gyp
- Semver 7 dependency analysis fails HOT 1
- Dynamic require of .json where file extension is not provided
- How to make it work with babel? HOT 3
- Uncaught ReferenceError: __dirname is not defined HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from webpack-asset-relocator-loader.