2a2890cae6
We need to spread the module into an object instead of access the module exports that could not exist, to avoid triggering the warning. Fix the bad loader change introduced in #50548 ``` Attempted import error: './middleware.js' does not contain a default export (imported as ' mod'). - info Using locally built binary of @next/swc - warn You are using an experimental edge runtime, the API might change. - wait compiling... - warn ../../../../packages/next/dist/build/webpack/loaders/next-middleware-loader.js?abso lutePagePath=%2FUsers%2Fhuozhi%2Fworkspace%2Fnext.js%2Ftest%2Fe2e%2Fapp-dir%2Fapp%2Fmiddle ware.js&page=%2Fmiddleware&rootDir=%2FUsers%2Fhuozhi%2Fworkspace%2Fnext.js%2Ftest%2Fe2e%2F app-dir%2Fapp&matchers=! Attempted import error: './middleware.js' does not contain a default export (imported as ' mod'). - wait compiling... ``` |
||
---|---|---|
.. | ||
create-next-app | ||
eslint-config-next | ||
eslint-plugin-next | ||
font | ||
next | ||
next-bundle-analyzer | ||
next-codemod | ||
next-env | ||
next-mdx | ||
next-plugin-storybook | ||
next-polyfill-module | ||
next-polyfill-nomodule | ||
next-swc | ||
react-dev-overlay | ||
react-refresh-utils |