Jiachi Liu efdb87d134 Drop browser field for edge runtime (#35335) ... Related to #31678 For streaming pages, Nodejs runtime: setting global runtime to `"nodejs"` will work with default module resolution. Edge runtime: previously next.js will pick up browser field since it's the "similar" asset (unlike nodejs) to edge runtime but browser specific things like DOM api could breaks cause edge runtime is more like worker without dom runtime. This PR is to revert the main field resolution behavior. And if you have a library targeting multiple runtime with different fields, ideally is to make it more isomorphic and will be easy to use in edge runtime		2022-03-16 15:14:49 +00:00
..
app	Drop browser field for edge runtime (#35335)	2022-03-16 15:14:49 +00:00
switchable-runtime	Make concurrent features independent from the global runtime option (#35245)	2022-03-16 12:11:57 +00:00
test	Drop browser field for edge runtime (#35335)	2022-03-16 15:14:49 +00:00
unsupported-native-module	Make concurrent features independent from the global runtime option (#35245)	2022-03-16 12:11:57 +00:00