`fs` dependencies like that have caused issues before. the solution is typically something like

``` turbopack: { resolveAlias: { fs: { browser: './empty-module.js' }, }, }, ```

so different configuration but similar to what you would do in webpack.

i am unsure about the other wasm issue you mentioned... is there an issue describing it?

As for webpack, we will keep supporting it until we know there are no compatibility issues blocking people from migrating.