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
[5.91.0] "Fixed fs types" breaks outputFileSystem
compatibility with memfs
#18242
Comments
This is a working workaround: compiler.outputFileSystem = fs as typeof compiler.outputFileSystem; |
Please open an issue in memfs, they have broken fs types, I wrote them, but no feedback, I can't fix it here, sorry |
You can make sure to use this:
but problems only with memfs, because some methods have wrong types |
Anyway feel free to feedback |
I created this issue mostly to make sure you've noticed this problem, and you know that example in Webpack docs does not really work as is now. For my purposes, just forcing the assignment via TypeScript casting is fine, so I don't feel any urge to do anything else about it. |
Yeah, memfs works fine with webpack, we have a lot of tests, just the types problem |
I just hit this issue as well. It doesn't look like this has been reported in the |
Nah @michaelfaith , I got distracted by different stuff and never reported it. Please report it there if you have a moment :) |
Bug report
What is the current behavior?
After Webpack upgrade from v5.90.3 to 5.91.0 in an existing project, the TypeScript does not allow the code given in Custom File Systems docs because of typing conflict mismatch:
I guess the change for "Fixed fs types" led to a regression.
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
Other relevant information:
webpack version:
Node.js version:
Operating System:
Additional tools:
The text was updated successfully, but these errors were encountered: