You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Created BROKEN_LINKS_ANALYSIS.md to document an investigation into reported broken links on nextjs.org. This file details:
A list of 5 broken /docs links reported on nextjs.org.
Their correct target paths in the current vercel/next.js documentation.
The corresponding redirect rules to be implemented in vercel/front.
An investigation into a 6th reported broken link (/docs/app/api-reference/functions/not-found), concluding the source file exists and the issue is likely deployment-related in vercel/front.
Why?
To address and resolve reported broken links on nextjs.org by providing a clear action plan for the vercel/front repository. The investigation confirmed that the issues stem from external references (e.g., from /learn or /blog pages on nextjs.org) pointing to old or renamed documentation paths, rather than broken links within the vercel/next.js docs source itself.
How?
Performed a comprehensive search and validation of reported broken links within the vercel/next.js/docs folder.
Identified that the broken links are external references pointing to old or renamed documentation paths.
Mapped the old paths to their current, correct counterparts in the vercel/next.js documentation.
Documented the findings and proposed redirect rules in BROKEN_LINKS_ANALYSIS.md.
- Analyzed 28 broken links reported on nextjs.org
- Identified correct redirect targets for old documentation paths
- Documented that source files exist in vercel/next.js
- Redirects need to be implemented in vercel/front repo
Reference: Slack #feedback-docs 2026-01-27
Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch. Learn more about Cursor Agents
Jest encountered an unexpected token
Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.
Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.
By default "node_modules" folder is ignored by transformers.
Here's what you can do:
• If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
• If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
• To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
• If you need a custom transformation specify a "transform" option in your config.
• If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.
You'll find more details and examples of these config options in the docs:
https://jestjs.io/docs/configuration
For information about custom transformations, see:
https://jestjs.io/docs/code-transformation
Details:
/root/actions-runner/_work/next.js/next.js/test/e2e/url-deployment-id/url-deployment-id.test.ts:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import { nextTestSetup } from 'e2e-utils';
^^^^^^
SyntaxError: Cannot use import statement outside a module
at Runtime.createScriptFromCode (../node_modules/.pnpm/jest-runtime@29.7.0/node_modules/jest-runtime/build/index.js:1505:14)
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For Maintainers
What?
Created
BROKEN_LINKS_ANALYSIS.mdto document an investigation into reported broken links on nextjs.org. This file details:/docslinks reported on nextjs.org.vercel/next.jsdocumentation.vercel/front./docs/app/api-reference/functions/not-found), concluding the source file exists and the issue is likely deployment-related invercel/front.Why?
To address and resolve reported broken links on
nextjs.orgby providing a clear action plan for thevercel/frontrepository. The investigation confirmed that the issues stem from external references (e.g., from/learnor/blogpages onnextjs.org) pointing to old or renamed documentation paths, rather than broken links within thevercel/next.jsdocs source itself.How?
vercel/next.js/docsfolder.vercel/next.jsdocumentation.BROKEN_LINKS_ANALYSIS.md.Closes NEXT-
Fixes #
Slack Thread