- 21 Jun, 2023 12 commits
-
-
vercel-release-bot authored
-
vercel-release-bot authored
-
Shu Ding authored
Reverts vercel/next.js#51172 Fixes #51482.
-
Leah authored
You'll probably want to disable whitespace in the diff ## Description This allows for better editor support by using `describe` or functions called `describe` with the same syntax instead of custom names. Changes: - `nextTestSetup` can be used instead of `createNextDescribe` keeping the same behaviour but being called inside a `describe` "block" (not applied everywhere) - `getSnapshotTestDescribe` replaced with a custom `describe.each` - `sandbox` helper function for `acceptance`/`acceptance-app` merged into a single shared one - `outdent` to remove the indent from inline files in tests which helps with consistent snapshots
-
vercel-release-bot authored
-
JJ Kasper authored
x-ref: [slack thread](https://vercel.slack.com/archives/C03S8ED1DKM/p1686906407341689)
-
-
Tobias Koppers authored
Reverts vercel/next.js#50830
-
Shu Ding authored
-
Delba de Oliveira authored
- Add some basic error handling to the link validator action. - Avoid unnecessarily creating a new bot comment when the validation is successful. - Only scan .mdx files modified in the current PR for broken links.
-
Tobias Koppers authored
### What? this forces all tests to use turbopack independent of the way they invoke next dev ### Why? some tests were not running turbopack fixes WEB-1187
-
Jimmy Lai authored
follow up on #51413 where I kinda forgot to support parsing layout files in sub routes in a parallel segment. This should fix it by making sure that we check at all level of the app loader tree and by creating an implicit inner `children` for all parallel slot link NEXT-1301
-
- 20 Jun, 2023 13 commits
-
-
JJ Kasper authored
Removes `__` prefix and ensures it's available on client/server as expected. x-ref: [slack thread](https://vercel.slack.com/archives/C04TNLL0LSK/p1687197571572119)
-
Joshua Baker authored
<!-- 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 ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### 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 # --> ### What/Why The `console.log` call was running per request and polluting logs. ### Locally ``` $ next start - ready started server on 0.0.0.0:3000, url: http://localhost:3000 - info Loaded env from /next/.env.local - warn metadata.metadataBase is not set for resolving social open graph or twitter images, fallbacks to "http://localhost:3000". See https://nextjs.org/docs/app/api-reference/functions/generate-metadata#metadatabase ^C ``` ### Vercel <img width="352" alt="Screenshot 2023-06-20 at 12 08 56@2x" src="https://github.com/vercel/next.js/assets/160484/dee72cd3-aa4e-46d8-886f-9476b9345498"> Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
vercel-release-bot authored
-
Shu Ding authored
When working with React Server Components, it's essential to have a clear understanding of how they function and how to troubleshoot any errors that may arise. This PR adds links to our documentation whenever an error related to React Server Components occurs.
-
hustLer2k authored
useSearchParams() links to /docs/app/api-reference/functions/use-params instead of /docs/app/api-reference/functions/use-search-params
-
Tyler Lutz authored
Removes duplicate "to" in documentation.
-
Zack Tanner authored
### What? While looking into some things related to the FileSystemCache, I came across this typo introduced in #49227. Not sure how it's currently manifesting but figured it'd be worth correcting
-
Tyler Lutz authored
Removes extra word in env-key-not-allowed.md error
-
Delba de Oliveira authored
This PR notifies the global owners about new PRs, but Vercel Spaces will still rotate the selection of team members as reviewers ([docs](https://spaces-docs.vercel.sh/docs/code-owners#notify)).
-
Delba de Oliveira authored
This PR migrates and adapts the [validate docs links script from `next-site`](https://github.com/vercel/front/pull/23185). This script is triggered by a GitHub action whenever a file in the `/docs` folder is updated. If broken links are found in the docs, the check fails and we post a comment on the PR with a list of broken links. Co-authored-by:
Michael Novotny <446260+manovotny@users.noreply.github.com>
-
Jiachi Liu authored
Fixes font styles change introduced in #49782 ### Visuall Diff - After vs Before <img src="https://github.com/vercel/next.js/assets/4800338/92f6af3a-9728-4dc5-b3d0-b21eefd16164" width="400"> <img src="https://github.com/vercel/next.js/assets/4800338/df88c9dd-b710-4a0a-a1aa-131adb55efa6" width="400">
-
JJ Kasper authored
Reverts vercel/next.js#51406 This pnpm bump seems to be causing lockfile issues with the react versions which causes context issues since we need to share the same react version in the monorepo.
-
- 19 Jun, 2023 15 commits
-
-
Tyler Lutz authored
Change tranforming to transforming in 05-mdx.mdx
-
Wyatt Johnson authored
Fixes a linting issue with a MDX file that was updated.
-
Shu Ding authored
Currently an "action module" (files with `"use server"` on top) can be imported by both the server and client layers. In that case, we can't fork that action module into two modules (one on the server layer, one on the action layer), but only create it once on the server layer. This ensures that the action module instance doesn't get forked. Closes #50801. fix NEXT-1265
-
Tobias Koppers authored
CI runs with root, there is no sudo
-
Tobias Koppers authored
### What? * allow to use `runtime = "edge"` for app dir in turbopack * move common imports from next-app-loader to `packages/next/src/server/app-render/entry-base.ts` * move common turbopack code to communicate between JS and Rust into separate files ### Why? A lot test cases depend on edge rendering ### How? --------- Co-authored-by:Alex Kirszenberg <alex.kirszenberg@vercel.com>
-
Wisnu Wicaksono authored
-
Leo Driesch authored
-
vicsantizo authored
-
vicsantizo authored
-
Sonam Serchan authored
-
Lee Robinson authored
-
Alex Kirszenberg authored
This contains the original POC for `next build --turbo`. The implementation is _just enough_ to get pages building, and doesn't support the app router yet. I'll write more details here on the implementation and what the next steps are next week. Necessary changes on the Turbo side: https://github.com/vercel/turbo/pull/4998
-
Jimmy Lai authored
This PR fixes a bug in which the layout files were not picked up if they were direct children of a parallel route slot. Note: there's a bunch of other files that I've used for debugging that are not used for the test but I'm leaving them for future me. link NEXT-969
-
Jiachi Liu authored
Reverting unexpected pnpm-lock changes from https://github.com/vercel/next.js/commit/a3ef99acd9805dded24214c21ac9149952af73a7
-
Tyler Lutz authored
-