vercel[bot]
commented
2 weeks ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| speed-insights-astro | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 6, 2024 0:07am |
| speed-insights-nextjs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 6, 2024 0:07am |
| speed-insights-nuxt | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 6, 2024 0:07am |
| speed-insights-remix | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 6, 2024 0:07am |
| speed-insights-sveltekit | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 6, 2024 0:07am |
| speed-insights-vue | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 6, 2024 0:07am |
socket-security[bot]
📓 What's in there?
We've been reported that compute route could be using some search parameter names instead of path parameter names. This PR fixes it.
🧪 How to test?
It has been tested locally with various version of Next.js, both pages and app router, and a special version of the debug script (soon released) which prints collected metrics to console.
In the following snapshots, the page has a single
[slug]parameter, and autm_contentsearch parameter.❗ Notes to reviewers
Please note that I've updated our example next.js app to latest router, which includes a change how the Page component can access its path params. The Node.js version is required by Next@15. Finally,
@jest/globalsis needed because of biome (which we should consider migrating to, as well as vitest).