bda92a1be5
~Due to the entry preloading that was enabled by default in #65289, VS Code is no longer able to map symbols correctly for production builds. As a temporary solution, we can disable the preloading when a debugger is started until a proper fix is found.~ By optionally building the Next.js source code with `NEXT_SERVER_EVAL_SOURCE_MAPS=1` we can ensure, even with the bundled next server in the node runtime, that the original names are shown in the debug "Variables" section. In addition, the `sourceMapPathOverrides` are improved to cover the different variations of source mapping URLs. We can now also set breakpoints in the `example/...` and `test/e2e/...` server components. ~Supersedes #66229~ #### Before <img width="1276" alt="Screenshot 2024-05-27 at 21 36 52" src="https://github.com/vercel/next.js/assets/761683/f2840c35-f683-445d-bc95-cac9f719d8e7"> #### After <img width="1276" alt="Screenshot 2024-05-27 at 21 38 42" src="https://github.com/vercel/next.js/assets/761683/c801c123-3163-46c3-b442-5b72c0a5d51d"> |
||
---|---|---|
.. | ||
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-refresh-utils | ||
third-parties |