Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[rush] Next.js 16.1 uses symbolic links for its serverExternalPackages which conflicts with Rush.js caching

Open
#5,583 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
next.js, node.js

Research direction

Start with the linked reproduction at github.com/eliw00d/next-rush-16-1-cache-sym-link-repro and review the Zulip discussion about symlinks in the build cache. Reproduce the conflict with Next.js 16.1 and Rush, then determine the expected caching behavior before identifying a fix and regression coverage.

Written by the indexing model from the issue text.

Description

Summary

See original discussion here.

Repro steps

Repro here.

Expected result:

Actual result:

Details

Standard questions

Please answer these questions to help us investigate your issue more quickly:

Question Answer
@microsoft/rush globally installed version?
rushVersion from rush.json?
pnpmVersion, npmVersion, or yarnVersion from rush.json?
(if pnpm) useWorkspaces from pnpm-config.json?
Operating system?
Would you consider contributing a PR?
Node.js version (node -v)?
Dominant language
TypeScript
Stars
6.5k
Forks
708
Avg merge
4d 13h
Merged PRs (30d)
62

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/rushstack

All issues in microsoft/rushstack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.