Tim Neutkens f260328900 BREAKING CHANGE: Enable newNextLinkBehavior (#41459) ... - Enable newNextLinkBehavior. See #36436 - Run next/link codemod on test suite Note that from when this lands on apps trying canary will need to run the new-link codemod in order to upgrade. Ideally we have to detect `<a>` while rendering the new link and warn for it. Co-authored-by: Steven <steven@ceriously.com>		2022-10-17 21:20:28 -04:00
..
3rd-party-module/pages
basic-module/pages
basic-module-include-paths
basic-module-prepend-data
catch-all-module/pages/[...post]
compilation-and-prefixing
composes-basic/pages
composes-external/pages
data-url
dev-module/pages
dynamic-route-module/pages/[post]
external-url
hmr-module/pages
invalid-global
invalid-global-module
invalid-global-with-app
invalid-module
invalid-module-document
loader-order
multi-global
multi-global-reversed
multi-module/pages	BREAKING CHANGE: Enable newNextLinkBehavior (#41459)	2022-10-17 21:20:28 -04:00
multi-page	BREAKING CHANGE: Enable newNextLinkBehavior (#41459)	2022-10-17 21:20:28 -04:00
nested-global
nm-module
nm-module-nested
npm-import
npm-import-bad
npm-import-nested
prod-module/pages
single-global
single-global-src
unused/pages
url-global
url-global-asset-prefix-1
url-global-asset-prefix-2
url-global-partial	Move resolve-url-loader into Next.js (#32932)	2022-01-02 16:16:17 -06:00
valid-and-invalid-global
webpack-error	Replace node-sass test dependency with sass (#39053)	2022-07-26 23:12:54 -05:00
with-styled-jsx
with-tailwindcss
with-tailwindcss-and-purgecss	BREAKING CHANGE: Enable newNextLinkBehavior (#41459)	2022-10-17 21:20:28 -04:00
next.config.js