- 16 Oct, 2022 1 commit
-
-
Tim Neutkens authored
-
- 15 Oct, 2022 9 commits
-
-
Tim Neutkens authored
Renames `router.reload` to `router.refresh` to better reflect that it refreshes the rendered page instead of being a blank slate. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Sukka authored
The PR continues from #41392. In #41392 the `dev ? cache-busting : empty` is executed per stylesheet instead of per page rendering. Since rendering link tags would be a hot path at the server, it might have accidentally introduced a performance overhead. The PR fixes that. Note, this change also makes `Date.now()` only execute once instead of per stylesheets, however, this will most likely not cause any issues.
-
Tim Neutkens authored
Similar to #40872 `useSearchParams` now returns a `URLSearchParams` instance instead of a plain object. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
JJ Kasper authored
-
Tim Neutkens authored
Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Donny/강동윤 authored
This PR updates swc crates to https://github.com/swc-project/swc/commit/3ff55caa38e5b193652aa3a203da10fbbfe34511 This PR applies various improvements, and more importantly https://github.com/swc-project/swc/pull/6142
-
JJ Kasper authored
Ensures query params aren't included when parsing dynamic route params during query hydration for a middleware matched path. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` Fixes: [slack thread](https://vercel.slack.com/archives/C035J346QQL/p1665692236623799)
-
Sukka authored
Follows #41150, bump the server-side code pre-compile target to Node.js 14.0.0. This could also potentially reduce the size of the server bundle and increase the performance (less transformation and fewer inlined swc helpers). Co-authored-by:
Tim Neutkens <tim@timneutkens.nl> Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
- 14 Oct, 2022 8 commits
-
-
Hannes Bornö authored
Moves where the validation is made to make sure the error reaches the client. Tests that an error overlay is shown on the client. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
Justin Ridgewell authored
## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
JJ Kasper authored
These tests have been flakey for a quite a while and this blocks changes that are unrelated so this skips them for now. x-ref: https://github.com/vercel/next.js/actions/runs/3250190671/jobs/5333599972 x-ref: https://github.com/vercel/next.js/actions/runs/3219413821/jobs/5264815514
-
Tim Neutkens authored
-
Jiachi Liu authored
Since we have already bundled dependencies for server layer, so the shared deps chunk group is not needed anymore. Also changing to esm assets import with next internals for edge function and middleware build. The changes are originally from #41337, try to land them separately.
-
JJ Kasper authored
This ensures we don't re-use edge workers locally as they are meant to be isolated. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` Fixes: [slack thread](https://vercel.slack.com/archives/C035J346QQL/p1665708744315109)
-
Steven authored
BREAKING CHANGE: Rename `next/image` to `next/legacy/image` & rename `next/future/image` to `next/image` (#41399) This PR introduces breaking changes by renaming components. - Rename `next/image` to `next/legacy/image` - Rename `next/future/image` to `next/image` The diff is very confusing because both components are very similar so git got confused.
-
- 13 Oct, 2022 17 commits
-
-
JJ Kasper authored
-
Jimmy Lai authored
In this PR, I'm inlining the require for some of the modules that I noticed take a bit of time to evaluate on a cold boot and are not needed most of the time. With this, it's an extra ~15ms win on cold boots (tested locally) and we are now at around 68ms (started from 110+). ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
JJ Kasper authored
Ensures we delete the prefetch header when the path is static as it can't be honored and the full tree must be sent instead. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` x-ref: [slack thread](https://vercel.slack.com/archives/C035J346QQL/p1665610012952039?thread_ts=1665582783.184029&cid=C035J346QQL)
-
Néstor authored
Gracefully parse the environment package manager when calling `create-next-app` instead of passing extra arguments. Reference: #41090 ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` Co-authored-by:Balázs Orbán <info@balazsorban.com>
-
LongYinan authored
Build succeed https://github.com/vercel/next.js/actions/runs/3243091429
-
Damien Simonin Feugas authored
##
📖 What's in there? This is a follow-up for https://github.com/vercel/next.js/pull/40180 Someone made the good point that users may get directed to this error page while setting up middleware matchers. And that page has no information (yet) about it. ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:Balázs Orbán <18369201+balazsorban44@users.noreply.github.com>
-
Weston Thayer authored
MDX no longer supports GitHub flavored markdown (GFM) by default since v2, instead requiring a plugin: https://mdxjs.com/guides/gfm/ Since GFM is extremely popular (for example, you need it if you want to use markdown tables), this change paves the cow path, making it clear that next.config.mjs is now supported and allows you to import remark-gfm.
-
이선우 authored
This PR contains changes made by updating the next-pwa to version [`5.6.0`](https://github.com/shadowwalker/next-pwa/releases/tag/5.6.0) ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` - [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:
Balázs Orbán <18369201+balazsorban44@users.noreply.github.com>
-
Hassan El Mghari authored
Adding a Next.js example with Salesforce Commerce Cloud Co-authored-by:JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
Sukka authored
Continuation of #39664 The PR removes `?ts=` in the production mode. The corresponding e2e test case is also added. cc @shuding
-
Jimmy Lai authored
The `ReadOnlyHeaders` class extends the `Headers` class that is provided via a polyfill. This incurs some costs the first time it's created because we need to load that polyfill. This saves approximately 10ms on my machine on a cold request. This is only useful when a user does not access headers during the request of course and when the runtime does not support fetch naitvely. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Tim Neutkens authored
-
Hannes Bornö authored
Fixes tree shaking for font loaders in server components. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Tim Neutkens authored
Adds `next/navigation` and `next/headers` APIs. Docs will follow later.. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:
JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
Lee Robinson authored
To be a bit more clear. Co-authored-by:JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
teobler authored
close https://github.com/vercel/next.js/issues/41378 add tips for building first before running tests for contribute Nextjs ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint`
-
Steven authored
Fixes a bug in `next/future/image` where `onLoad` might not be called. This is the same workaround we added for `onError`.
-
- 12 Oct, 2022 5 commits
-
-
Balázs Orbán authored
Ref: #41344 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Sukka authored
The PR continues from #41164. `next/script` with `beforeInteractive` should not block the hydration, **but the `polyfill-nomodule` *should* block the hydration** (and should be loaded before other scripts), as `polyfill-nomodule` includes multiple polyfills to even execute `main-app.[hash].js` properly on old browsers (`Array.prototype.includes`, `String.prototype.startsWith`, etc.). Without `polyfill-nomodule` being loaded first, the entire bootstrap/hydration process might not even work on old browsers. So it should not be loaded through `__next_s`. cc @shuding Co-authored-by:Shu Ding <g@shud.in>
-
JJ Kasper authored
-
Tim Neutkens authored
- Remove unused code - Keep rendering underlying component tree when there is a build error - Move error catch up one level ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Shu Ding authored
The way we currently track server CSS imports is to collect CSS files that each **module** depends on. This happens on the module graph level which is a global thing and cannot be tree-shaken properly (check the enabled test for more details). In this PR we collect another information, of CSS files that each **entrypoint** depends on. This is the CSS list after tree-shaken on the entry level. By intersecting these CSS imports with the module-level CSS imports, we can get the final used CSS imports for each _layout_. cc @hanneslund ## Bug - [ ] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-