Naoyuki Kanezawa 9e53af8e30 Fix next node buildin module error message for edge runtime (#36434) ... - improve the message for importing node builtin module on edge runtime - fix to show the message on overlay of error browser with `next dev` - fix https://github.com/vercel/next.js/issues/36237 The message is NOT shown when using edge runtime (not middleware) since I cannot find a way to detect a webpack compilation is for edge runtime. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint`		2022-05-02 15:21:40 +00:00
..
index.ts	Fix next node buildin module error message for edge runtime (#36434)	2022-05-02 15:21:40 +00:00
parseBabel.ts	Pre-compile more dependencies continued (#32679)	2021-12-21 16:13:45 +01:00
parseCss.ts	Fix typos (#35683)	2022-03-28 22:53:51 -05:00
parseNotFoundError.ts	Fix next node buildin module error message for edge runtime (#36434)	2022-05-02 15:21:40 +00:00
parseScss.ts	Pre-compile more dependencies continued (#32679)	2021-12-21 16:13:45 +01:00
simpleWebpackError.ts	partially migrate to webpack 5 types (#30189)	2021-10-24 23:04:26 +02:00
webpackModuleError.ts	Fix next node buildin module error message for edge runtime (#36434)	2022-05-02 15:21:40 +00:00