-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
in-memory filesystem for webpack assets #83
Conversation
Current coverage is 85.44% (diff: 96.70%)@@ master #83 diff @@
==========================================
Files 16 18 +2
Lines 398 474 +76
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 327 405 +78
+ Misses 71 69 -2
Partials 0 0
|
@serut |
Amazing work @zinserjan, it fully works on my project ! I read tests that you wrote and they are very good !
Well done. |
Nice! But I think that changing files which are required inside |
All webpack assets are now handled by an in memory filesystem as suggested in #25. No files are written to disk.
How does it work?
At the moment this works only for
.js
files, cause we need to register each file extension manually. But this should be fine as nodejs only understands.js
,.json
and.node
files and as far as I know webpack emits only.js
files.Tasks:
debugger
statements)