Comments (4)
I've done this because it failed reloading loaders when in watch mode and a loader has changed.
It can fail if you rely on require
in a loader return the same instance as a require
not in a loader.
Multi process compiling is on roadmap and this will make these loaders fail too.
Why exactly do your code fail?
You can stay locked at 0.5.8 until we have a solution. I'm on vacation for a week by now, sorry.
from webpack.
My module nodeclass
takes so-called descriptor-objects and creates a class function. Defining a class looks like:
var MyClass = new Class("MyClass", {
Extends: require("./MySuperClass.class.js"),
init: function () {}
});
In order to compute all inherited properties I have to save every descriptor in a registry. Now the registry can't save those descriptors because it is created from scratch for every new class.
I think it's ok that webpack
needs to be restarted if a loader has changed. Changing a loader is not the same like changing a module that will be bundled.
Currently webpack
removes the whole cache before every single file. This is almost like starting a new process for every file.
from webpack.
Hmm.. i should undo this change and make multi process building as opt-in (per loader) feature. Webpack should throw an warning or an error if a loader is changed.
from webpack.
I'm glad that I could convince you ๐
from webpack.
Related Issues (20)
- Webpack build error for second time HOT 1
- `exportsPresence` does not work for unused imports HOT 3
- Implement ability to use "node:" prefixes for Node.js core modules HOT 1
- mangled exports breaks with destructuring assignment of JSON imports HOT 7
- there are confusing JDocs code
- Potential bug issues
- Webpack is not resolving node_modules specified in `resolve.modules` property.
- Dynamically loading chunks
- [Code implementation issues] ArrayQueue
- [feature] create cli HOT 3
- Not able to build node script
- bootstrap:27 Uncaught TypeError: __webpack_require__.nmd is not a function
- Self-reference dependency has unused export name when imported inside of a web worker
- support `import.meta.dirname` and `import.meta.filename` HOT 2
- <!-- identifier: admin-actions -->
- Remote into Web Component from React giving an error saying " Module does not exist in container"
- Multiple DefinePlugin instances cause aggressive cache invalidation due to collisions HOT 7
- Webpack fails when importing module
- import .scss build to js, the exported mapping is inconsistent with the usageใUrgent!!ใ
- Unused code elimination and deduplication is not applied when using sass's api: 'legacy' setting
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.