vercel__next.js

skills/vercel__next.js

Fork 0

mirror of https://github.com/vercel/next.js.git synced 2026-09-20 02:25:18 +08:00

Commit Graph

Author	SHA1	Message	Date
Jiwon Choi	d7aa66c345	Remove generated error codes (#97687 ) ### Why? Should come up with better solution that does not block PRs with git conflict x-ref: https://vercel.slack.com/archives/C02CDC2ALJH/p1785263902728189?thread_ts=1785263687.502649&cid=C02CDC2ALJH ### How? - Delete `errors.json`, the error-code SWC plugin, generated WASM, merge driver, and validation/build tooling. - Stop attaching error codes to server-rendering digests, redboxes, and telemetry; native `Error.code` and `Error.name` remain available where applicable. - Remove the development-overlay error feedback UI, middleware, and telemetry event that depended on stable codes. - Update fixtures, snapshots, and guidance for code-free errors and numeric-only digests. <!-- NEXT_JS_LLM -->	2026-08-21 22:45:12 +02:00
Janka Uryga	1bfe63a6d0	auto-enable errors.json merge driver (#83420 ) The merge driver for `errors.json` has been around for a while, and seems to work without issues. This PR enables it by default by installing it in `postinstall`(via the existing `git-configure.mjs` script which is invoked from there already) It also adds `scripts/merge-errors-json/uninstall` to temporarily disable it in case of issues. If the driver crashes, we'll also print instructions on how to disable it.	2025-09-04 18:08:47 +02:00
Steven	1662362d12	chore: fix postinstall when using tarball (#60443 ) The postinstall script was failing In the case when you download [a zip](https://codeload.github.com/vercel/next.js/zip/refs/heads/canary) of the repo. This PR fixes it so that `git config` can fail silently in that case when the repo is not using git. - Related to https://github.com/nodejs/citgm/pull/1044 Closes NEXT-2036	2024-01-09 17:37:49 -05:00

Author

SHA1

Message

Date

Jiwon Choi

d7aa66c345

Remove generated error codes (#97687 )

### Why?

Should come up with better solution that does not block PRs with git
conflict

x-ref:
https://vercel.slack.com/archives/C02CDC2ALJH/p1785263902728189?thread_ts=1785263687.502649&cid=C02CDC2ALJH

### How?

- Delete `errors.json`, the error-code SWC plugin, generated WASM, merge
driver, and validation/build tooling.
- Stop attaching error codes to server-rendering digests, redboxes, and
telemetry; native `Error.code` and `Error.name` remain available where
applicable.
- Remove the development-overlay error feedback UI, middleware, and
telemetry event that depended on stable codes.
- Update fixtures, snapshots, and guidance for code-free errors and
numeric-only digests.

<!-- NEXT_JS_LLM -->

2026-08-21 22:45:12 +02:00

Janka Uryga

1bfe63a6d0

auto-enable errors.json merge driver (#83420 )

The merge driver for `errors.json` has been around for a while, and
seems to work without issues. This PR enables it by default by
installing it in `postinstall`(via the existing `git-configure.mjs`
script which is invoked from there already)

It also adds `scripts/merge-errors-json/uninstall` to temporarily
disable it in case of issues. If the driver crashes, we'll also print
instructions on how to disable it.

2025-09-04 18:08:47 +02:00

Steven

1662362d12

chore: fix postinstall when using tarball (#60443 )

The postinstall script was failing In the case when you download [a
zip](https://codeload.github.com/vercel/next.js/zip/refs/heads/canary)
of the repo.

This PR fixes it so that `git config` can fail silently in that case
when the repo is not using git.

- Related to https://github.com/nodejs/citgm/pull/1044

Closes NEXT-2036

2024-01-09 17:37:49 -05:00

3 Commits