Skip to content

Conversation

@sequencerr
Copy link
Contributor

delete is reserved word

delete is reserved word
@ijjk ijjk added the Documentation Related to Next.js' official documentation. label Nov 13, 2025
@ijjk
Copy link
Member

ijjk commented Nov 13, 2025

Allow CI Workflow Run

  • approve CI run for commit: 011e849

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Copy link
Collaborator

@icyJoseph icyJoseph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome find! 🎉 ~ This had been there for two years!

I ran a search for other keywords and such (w/ an agent) and looks like this was the only faulty usage, but if you do find more please send PRs 🚀

@icyJoseph icyJoseph enabled auto-merge (squash) November 13, 2025 20:05
@icyJoseph icyJoseph merged commit ef051ff into vercel:canary Nov 13, 2025
63 checks passed
Moroshima pushed a commit to Moroshima/next.js that referenced this pull request Nov 20, 2025
delete is reserved word

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Related to Next.js' official documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants