-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
feat(webpack): migrate to memfs
#27652
Conversation
Run & review this pull request in StackBlitz Codeflow. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 2.x #27652 /- ##
==========================================
- Coverage 66.23% 65.86% -0.38%
==========================================
Files 93 93
Lines 4123 4139 16
Branches 1170 1172 2
==========================================
- Hits 2731 2726 -5
- Misses 1126 1145 19
- Partials 266 268 2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
memfs
memfs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is ancient history for me to comment haha, i would recommand to fork memfs or even inline it to avoid fs workaround
🔗 Linked issue
resolves #26435
related #21804, #20564
📚 Description
This migrates from 'memory-fs' to 'memfs'.
This is necessary because of a breaking change with 'webpack-dev-middleware' in 5.0.0 . But sticking to 5.0.0 would mean that we would have a known security vulnerability with path traversal: GHSA-wr3j-pwj9-hqq6.