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

chore(test): vite rebuild fixture output breaks the next `pnpm build`

Open Beginner friendly
#4,744 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@AdarshYadav9 is already working on this.

Since Oct 7, 2026.

  • #4746 by @AdarshYadav9 — open

Assessment

Difficulty
2/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript, vite
Domain
build-system

Research direction

Start in test/vite/rebuild.test.ts, where the fixture output in test/vite/rebuild-fixture/dist is removed only before the run — add cleanup after it, or alternatively add a test/**/dist entry to the exclude in the root tsconfig.json. Verify by running pnpm test:rolldown (or test:rollup) followed by pnpm build and confirming the TS4094 error from rolldown-plugin-dts no longer appears without manually deleting the folder.

Written by the indexing model from the issue text.

Description

After running pnpm test:rolldown (or test:rollup), test/vite/rebuild.test.ts leaves its build output in test/vite/rebuild-fixture/dist (gitignored). The next pnpm build then fails in rolldown-plugin-dts because tsgo picks up dist/server/_libs/h3+rou3+srvx.mjs from that folder and reports TS4094: Property '#body' of exported anonymous class type may not be private or protected (allowJs is on and the root tsconfig.json does not exclude it). Deleting the folder makes the build pass again.

Possible fixes: clean up dist at the end of the test (it is only removed before the run today), and/or exclude test/**/dist in tsconfig.json.

Reported with AI assistance.

Dominant language
TypeScript
Stars
11.3k
Forks
914
Avg merge
1d 3h
Merged PRs (30d)
81

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 nitrojs/nitro

All issues in nitrojs/nitro

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.