Fodor Zoltan
Fodor Zoltan
See https://github.com/electron/electron/issues/10732#issuecomment-1061163988
@askurat No I haven't. It would be nice to see some movement here.
I am encountering this in a different situation. The callstack seems different as well than what was posted here previously. On the other hand I am not trying to use...
Yeah this would then be a real nice feature. Question still remains: is there only treebuilding happening? or is there also compilation upon the subtree? or something else that is...
Ok I am no expert in this. Hope it's possible tho. By compilation I meant running the files through loaders.
> yes, this is a part of creating module graph. Just to make sure I understand correctly. In the above example repo babel will be ran on each file loaded...
I will do some more fiddleing to see the impact of the discovery vs loaders running on graph building. But my initial thought is that for graph building needing loaders...
I've made another branch https://github.com/archfz/webpack-treeshake-issue/tree/no_babel_on_modules and here I transformed all jsx in the 3rd party packages to js. I've also made babel not parse files from node modules. With this...
Maybe loaders should mark themselves sideeffect free, or by default be and can opt out.
I also have this issue. What I would like to do more specifically, is to return my own codes for error. But seemingly this is impossible. I have found `env.throw_error`...