You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm literally just using new HardSourceWebpackPlugin(); so I don't think I'm doing anything wrong, but this is what's being generated by the plugin right now:
As you can see, it's creating a brand new node_modules inside my src folder, rather than using my actual node_modules folder (which is one level up).
Is this meant to be the default behavior with this folder structure? Seems kind of unusual.
The text was updated successfully, but these errors were encountered:
@rococode The default creates a cache directory relative to your webpack context option. If thats not set it makes the path relative to the current working directory.
So either your context points into src, or you're building from that directory. I think thats fine and hard-source should probably be a little smarter. But I'm not sure if I'll make that change in 0.5.x, so that may be a bit before the default changes in probably 0.6.x.
You can work around this by setting cacheDirectory in the options to HardSource.
I'm literally just using
new HardSourceWebpackPlugin();
so I don't think I'm doing anything wrong, but this is what's being generated by the plugin right now:As you can see, it's creating a brand new
node_modules
inside mysrc
folder, rather than using my actualnode_modules
folder (which is one level up).Is this meant to be the default behavior with this folder structure? Seems kind of unusual.
The text was updated successfully, but these errors were encountered: