- 26 Apr, 2023 2 commits
-
-
vercel-release-bot authored
-
- 25 Apr, 2023 12 commits
-
-
Shu Ding authored
Fixes the ``` TypeError: Cannot read properties of undefined (reading 'strict') at writeConfigurationDefaults ``` error. Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Shu Ding authored
This PR adds an `AsyncLocalStorage` wrapper to the action handler, so underlying function calls can tell if it's running in that.
-
Shu Ding authored
It makes more sense to use the `FormData` from `@edge-runtime/primitives` to ensure the version and implementation are aligned, and avoid importing extra modules (as we always import the Edge Runtime).
-
Tobias Koppers authored
### What? Fix the query for app dir ### Why? it's not correct in app dir
-
Shu Ding authored
Part of #47759 (which had been reverted twice so here we only land a part of the change), relates to NEXT-926. Thanks to #48506 we can soon switch between these two channels during runtime. Also fixes a problem of `renderKind` (only revealed after upgrading React), it should be also based on the `match` kind.
-
Shu Ding authored
This is currently an overhead, that we check a module's layer (`mod.buildInfo.rsc?.type === RSC_MODULE_TYPES.client`) and put all client modules in the client reference manifest, but the manifest is only used for accessing these entry modules. So here we change the util to check if it's an client entry instead. With this change the client manifest of a test app decreased from 177 KB to 70 KB. Ref: https://github.com/vercel/next.js/blob/5b609e264f56e6e7c6e230d88ad444650b5b6ba9/packages/next/src/build/analysis/get-page-static-info.ts#L50-L64
-
Jiachi Liu authored
Improve array resolving in metadata, remove ts comments for errors
-
vercel-release-bot authored
-
Tim Neutkens authored
### What? Mux reported that their website does not scroll to hash when clicking a search result. Found it's related to `server-patch` triggering and overriding the hashFragment. That should be preserved similarly to `apply`. ### How? handleMutable had a default of `null` instead of using the existing value. It should use the existing value.
-
Donny/강동윤 authored
### What? Update `@swc/helpers` to `v0.5.1`. ### Why? Webpack merges `@swc/helpers@v0.4.x` and `@swc/helpers@v0.5.x`, due to `resolve.alias` config in https://github.com/vercel/next.js/blob/2f6ff0dab330b854c43a1773be2fe739c3582419/packages/next/src/build/webpack-config.ts#L1070-L1072 To workaround it, `@swc/helpers@v0.5.1` reexports from entries just like `v0.4`. ### How? Closes WEB-948 Fixes #48593
-
vercel-release-bot authored
-
- 24 Apr, 2023 17 commits
-
-
vercel-release-bot authored
-
Steven authored
This should fix the following error: ``` npm ERR! 422 Unprocessable Entity - PUT https://registry.npmjs.org/@next%2fswc-darwin-x64 - Failed to validate repository information: package.json: "repository.url" is "undefined", expected to match "git+https://github.com/vercel/next.js" from provenance ``` https://github.com/vercel/next.js/actions/runs/4787411938/jobs/8512829488#step:10:74 - Related to https://github.com/vercel/next.js/pull/48757
-
Philip Nguyen authored
-
Preston Landers authored
A change here: (#48202) 958150d1 Caused a URL to be joined with `path.join`, which on Windows inserts a backslash character. Changing to `path.posix.join` fixes this. Breaks next build on Windows when paths like `favicon.ico` are in the source dir. Fixes #48603
-
Jiachi Liu authored
When you're using `config` object with `runtime` we'll show a warning and recomment you to move to `export const runtime = ...` for runtime property as it's documented as recommended. This PR adds a error for `next build` to avoid logs are truncated during multi-workers build and you're aware of the config which doesn't take effect with seeing the error Follow up for #48630 link [NEXT-426](https://linear.app/vercel/issue/NEXT-426)
-
Shu Ding authored
We currently use `URLSearchParams` to represent `FormData` but it's not really the same thing. And in Node.js 16 there's no `FormData` available so we can polyfill it via Undici.
-
vercel-release-bot authored
-
Steven authored
Co-authored-by:
Jiachi Liu <inbox@huozhi.im> Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Jan Kaifer authored
-
Shu Ding authored
Interesting learning from [this](https://sun0day.github.io/blog/vite/why-vite4_3-is-faster.html#fs-realpathsync-issue), that `fs.realpathSync` is 70x slower than `fs.realpathSync.native`. Kudos to the Vite team!
-
Jan Kaifer authored
-
Chris authored
Updates the name of Next.js Analytics to Next.js Speed Insights closes ALY-579 --------- Co-authored-by:
Steven <steven@ceriously.com> Co-authored-by:
Tim Neutkens <tim@timneutkens.nl>
-
Alex Kirszenberg authored
This fixes a perf regression introduced in the chunking refactor, where we would be eagerly generating all assets from the web entry and fallback sources. See https://github.com/vercel/turbo/pull/4679 This also brings the following updates from vercel/turbo: * https://github.com/vercel/turbo/pull/4669 <!-- Tobias Koppers - make the invalidation reason easier to read --> * https://github.com/vercel/turbo/pull/4670 <!-- Tobias Koppers - dev-server content might change any time, we can't cache them --> * https://github.com/vercel/turbo/pull/4653 <!-- OJ Kwon - fix(ecmascript): displayname for styled_components --> * https://github.com/vercel/turbo/pull/4679 <!-- Alex Kirszenberg - Lazy DevHtmlAsset chunk generation --> (this change)
-
vercel-release-bot authored
-
Tim Neutkens authored
This reverts commit 1c007cee.
-
vercel-release-bot authored
-
Tim Neutkens authored
### What? Compiles Next.js core files using the same default target as client-side files, ensuring that `async`/`await` and such are not turned into generators. The client-side files are all opted into compilation during dev/build already so if you create a browserslist config that will still apply in the same way. This change only changes the output of the core files. ### How? Moved the default we use in Next.js into a separate `.js` file so that it can be imported from the taskfile-swc plugin, this way we're using the same defaults. <!-- 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 or adding/fixing 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 # -->
-
- 23 Apr, 2023 6 commits
-
-
vercel-release-bot authored
-
Steven authored
Draft Mode is very similar to Preview Mode but doesn't include any additional data. This PR implements support for Draft Mode in `pages` and a future PR will implement support in `app`. fix NEXT-992
-
Afonso Jorge Ramos authored
Hey! Hope this can help anyone dealing with this in the future. I'm also using the `TinaMarkdown` provider to generate my MDX and one of the things that I've found helpful so that the image was better handled in the browser was to set position to `undefined`, as it was the only way to unset it from `absolute`, which was affecting the visual aspect of the page. Co-authored-by:Steven <229881+styfle@users.noreply.github.com>
-
Sreetam Das authored
The TS plugin incorrectly gives a warning for the `reset` prop in the `global-error.tsx` file. This was previously reported and fixed for the `error.tsx` file. - https://github.com/vercel/next.js/issues/46573 - https://github.com/vercel/next.js/pull/46898 --- You can see a reproduction on [CodeSandbox](https://codesandbox.io/p/sandbox/summer-dawn-b0gydg?file=%2Fapp%2Flayout.tsx&selection=%5B%7B%22endColumn%22%3A16%2C%22endLineNumber%22%3A18%2C%22startColumn%22%3A16%2C%22startLineNumber%22%3A18%7D%5D) — `global-error.tsx`'s `reset` prop has the following warning: ``` Props must be serializable for components in the "use client" entry file, "reset" is invalid. ts(71007) ``` I haven't filed an issue for this yet since this was a simple enough fix, but happy to create one if needed :)
-
-
Wyatt Fry authored
"ran" is conjugated, which cannot be used after the verb "to be", only the infinitive "run" is correct here.
-
- 22 Apr, 2023 1 commit
-
-
Jiachi Liu authored
Reverts vercel/next.js#48688 fix NEXT-1011
-
- 21 Apr, 2023 2 commits
-
-
Shu Ding authored
Feedback form @MaxLeiter, that we shouldn't tell the user to add "use client" in this case: 
-
Shu Ding authored
When sending a multipart form data, we currently wait until the entire update finishes before we decode it via `decodeReply`. This way is universal in both runtimes (as we don't have `decodeReplyFromBusboy` in Edge), but also not efficient. This PR changes it to use `decodeReplyFromBusboy` in the Node runtime, which can decode the payload during streaming as well as file update support.
-