hardfist

even though entry key is not standardized, since uses can customize webpack's mainfield ```js module.exports = { //... resolve: { mainFields: ['browserModern', 'browser', 'module', 'main'] // load modern first }...

@developit what if the library node && library support have different implementation, then which module should points to? node implementation or browser implementation?

how does bundler know about that？ by main fields？

@drcmda normally you call createNamedContext in componentDidMount and call removeNamedContext in compoentWillUnmount,but if you really need use createNamedContext in constructor, your can free local state in componentWillMont on server side...

@Lmmmmmm-bb please help check it in latest version

> But I don't know why the "latest" version installs "0.1.0". maybe your lockfile locks the version to 0.1.0

I read https://esbuild.github.io/faq/#top-level-var and know the design reason, but it conflicts with other bundler's default behavior which may make code runs successfully on esbuild but fails on other bundler

> Metadata for both input files and output files is accessible with the `metafile` feature: https://esbuild.github.io/api/#metafile its not easy to get chunk info from metafile when deals with multi entry

we don't use stable channel please check your `rustup show` result to see whether you use the right nightly version  we configure the rust version in https://github.com/web-infra-dev/rspack/blob/main/rust-toolchain.toml, if your...

we should not run release build in test