hardfist

不是很理解，或许你可以提供个demo帮助理解

> Run @rspack/core in the browser. Since rspack interface exposed by node_binding is missing lots of features, such as option nomalization, essential plugins, loader context, which make it hard to...

> tokio: async tokio::fs => sync std::fs seems unnecessary cause the ntaivefs is used for native OS, we can just ship a browser_fs for browser side which even don't need...

I mean `tokio::fs` should only be used in NativeFileSystem https://github.com/web-infra-dev/rspack/blob/5a6ed3137e20fad8f9ca3d6b1842178fa22335fa/crates/rspack_fs/src/native_fs.rs#L19 which maybe not necessary for browser, so you could choose either ways * change tokio::fs to std::fs in NativeFileSystem when...

> rspack_futures: its dependency async-scoped depends on tokio multi-thread rt. not sure rspack_futures can be replaced with with tokio_stream and wether tokio_stream can be compatible with wasm > persistence cache:...

@CPunisher do you plan to finish all tasks in this PR or separated into multi PRs

that depends on how long would it take, I suggest when you can successfully compile rspack to wasm target(no need to actually run in browser) we can merge it first...

> @hardfist > > > don't remove wrap iife even when use set iife:false, and give warning to users > > I think it is better for DX agree, I...

please provide full error report, the reason most lie in plugin use some unsupported hook so we need more error info

Even we can support beforeModuleIds hook, it will cause huge Rust | JS communication which may slow the build a lot > The default/current behavior for generating module ids in...