-
-
Notifications
You must be signed in to change notification settings - Fork 376
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
fix: directly used mkdirp instead of through Webpack #436
Conversation
Fixes Webpack 5 usage by no longer requiring the removed webpack/lib/node/NodeOutputFileSystem
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.
/cc @hiroppy
Thanks. |
When will a new release be cut? |
Could we please have a release to benefit from this update and use it again with latest versions of webpack 5? |
In TODO, release will be tomorrow |
Great, thanks @evilebottnawi |
Any word on releasing this? |
@natew yes, today, we find some problems with api and redesigning it in the next version, so it took us a little longer |
Fixes Webpack 5 usage by no longer requiring the removed webpack/lib/node/NodeOutputFileSystem
This PR contains a:
Motivation / Use-Case
Fixes #435.
Breaking Changes
Introduces dependency on
mkdirp
, which was only transient throughwebpack
before.