Balázs Orbán
33db463fe4
chore: upgrade jest ( #56909 )
...
### What?
Upgrade jest to its latest version
### Why?
#56899 fails because historically Jest stripped the globals in Node.js, but 28+ isn't doing that anymore. If we upgrade, we don't have to keep track of Node.js globals and when they are added. This will be useful in removing even more polyfills for things that are natively shipped in Node.js now.
### How?
Jest 29 introduced a change to the snapshot format: https://jestjs.io/blog/2022/08/25/jest-29
First, I tried setting the old compat option to not require updating snapshots, but some tests were still failing: https://dev.azure.com/nextjs/next.js/_build/results?buildId=70633&view=logs&j=8af7cf9c-43a1-584d-6f5c-57bad8880974&t=7ae70e63-3625-50f4-6764-5b3e72b4bd7a&l=273 So going through the pain now instead.
2023-10-19 17:38:24 +00:00
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
JJ Kasper
a92a5caec2
Update test set-up to leverage playwright when able to ( #28634 )
...
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2021-09-13 14:36:25 +02:00
Jan Potoms
e56a6add8d
Add test for query param bug #15233 ( #15238 )
...
Fixes https://github.com/vercel/next.js/issues/15233
2020-07-16 22:47:46 +00:00
Joe Haddad
ac5b2acd12
Fix dynamic route encoding for NextLinks ( #14281 )
2020-06-29 16:44:43 -04:00
