- 15 Apr, 2024 27 commits
-
-
vercel-release-bot authored
-
Will Binns-Smith authored
Turbopack: don’t show long internal stack traces on build errors Fixes PACK-2909 Looks like this may have been introduced in #61929, when code was moved out of `setup-dev-bundler.ts`, `ModuleBuildError` was duplicated and no longer satisfied the `instanceof` check. Closes PACK-2951 -
Jiachi Liu authored
Remove the `this.exportRuntime` flag in build manifest plugin where it's always true Closes NEXT-3118
-
Will Binns-Smith authored
Resolves #64412 This adds a client transition to the app route `ModuleAssetContext` and the corresponding transforms so that client components can be safely imported and referenced (as their proxies) in app routes. Test Plan: Added an integration test Closes PACK-2964
-
JJ Kasper authored
Updates to latest version which bumps Node.js version to avoid v16 deprecation. Closes NEXT-3120
-
vercel-release-bot authored
-
Tobias Koppers authored
* https://github.com/vercel/turbo/pull/7858 <!-- Tobias Koppers - refactor GlobalCssAsset to fix dynamic import of css --> * https://github.com/vercel/turbo/pull/7944 <!-- Will Binns-Smith - Update lockfile for compatibility with next.js --> * https://github.com/vercel/turbo/pull/7936 <!-- Tobias Koppers - fix panic when searching an the root span --> * https://github.com/vercel/turbo/pull/7959 <!-- Tobias Koppers - fix missing async loader -->
-
Kenji authored
There's a TODO above the links, I didn't understand if it was related to this PR as the domain was already authjs.dev ### What? - Fixes the link to NextAuth in the `Examples` section ### How? - Changes https://authjs.dev/guides/upgrade-to-v5 to https://authjs.dev/getting-started/migrating-to-v5Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
Jiwon Choi authored
cc @shuding CI run failed after #63053 on turbo production, which had not yet been targeted for turbo. x-ref: #63103 --------- Co-authored-by:
JJ Kasper <22380829+ijjk@users.noreply.github.com> Co-authored-by:
Leah <8845940+ForsakenHarmony@users.noreply.github.com> Co-authored-by:
Jiachi Liu <inbox@huozhi.im>
-
Tobias Koppers authored
### What? The production chunking plugin shouldn't be enabled in development ### Why? It doesn't handle HMR yet Closes PACK-2956
-
Jiwon Choi authored
### What? The string value of `Metadata.openGraph.emails` throws error: ```tsx export const metadata = { openGraph: { type: 'article', emails: 'author@vercel.com', }, }; ``` Error: ```sh r.map is not a function ``` The type is: ```tsx type OpenGraphMetadata = { // ... emails?: string | Array<string> } ``` ### Why? Basic values such as `emails` and `phoneNumbers` were not included when `ogType` was set while resolving the values. ### How? Include basic values when resolving the metadata. Fixes #63415 -
Ethan Arrowood authored
This fixes and improves the `lib/helpers/install.ts` file (`install()`) method to better support pnpm and properly respect the `root` argument. I encountered an issue where by running `next <command> <project-dir>`, and the `<command>` involved installing missing dependencies (like `lint` or my upcoming `experimental-test`), it was not executing pnpm in my `<project-dir>` because pnpm doesn't have a `--cwd` flag. Closes NEXT-3092 Co-authored-by:Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
vercel-release-bot authored
-
JJ Kasper authored
This ensures we properly skip calling a fetch during build-time that has `cache: 'no-store'` as it should only be called during runtime instead. Fixes: https://github.com/vercel/next.js/issues/64462 Closes NEXT-3114
-
Jiwon Choi authored
I'm assuming leaving keywords blank is intended, but with
🖤 for Next.js, I added 10 keywords to increase the traction of users. - react - web - server - node - nextjs - vercel Also, included relative keywords that can be easily accessed from the landing of [npm](https://www.npmjs.com). - framework - front-end - back-end - cli  Co-authored-by:Shu Ding <g@shud.in>
-
Jiwon Choi authored
## Why? For multi-root layouts (route groups on the root with their root layouts, no layout file on the root), it is not possible to use global `not-found` since the `layout` is missing on the root. ```sh . └── app/ ├── (main)/ │ └── layout.js ├── (sub)/ │ └── layout.js └── not-found.js --> ERR: missing layout ``` Current Behavior: ```sh not-found.js doesn't have a root layout. To fix this error, make sure every page has a root layout. ``` ## What? Let multi-root layouts also benefit from the global `not-found`. ## How? Wrap root `not-found` with default layout if root layout does not exist. Although this solution is not `multi-root` specific, it won't produce critical issues since a root `layout` is required for other cases. Fixes #55191 #54980 #59180 -
vercel-release-bot authored
-
Sebastian Silbermann authored
-
Arne Wiese authored
Super small PR - "oustide" should be "outside" <!-- 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 # -->
-
Jeffrey Zutt authored
### What? We strip the `traceparent` header from the cache-key. ### Why? The traceparent header forms part of the W3C Trace Context standard, installed to track individual HTTP requests from start to end across multiple services. That means each individual HTTP request will have a unique traceparent value, reflecting its unique journey across servers and services. If we include the traceparent header in the cache key, the uniqueness of the traceparent means the cache key would always be different even for requests that should yield the same response. This would cause the cache to always miss and re-process the request. Effectively rendering fetch-cache useless. Co-authored-by:Jeffrey <jeffrey@jeffreyzutt.nl>
-
Damien Simonin Feugas authored
BREAKING CHANGE: remove deprecated analyticsId from config, and the corresponding performance-relayer files and tests (#64199) ###
🤔 What's in there? We've deprecated config's `analyticsId` in 14.1.1 [almost 3 months ago](https://github.com/vercel/next.js/releases/tag/v14.1.1-canary.2). Users can opt in fot `@vercel/speed-insights`, or use `useReportWebVitals` to report to any provider they'd like. This PR: - removes `analyticsId` key from configuration - stops setting `__NEXT_PUBLIC_ANALYTICS_ID` env variable when the key was present - stops injecting `performance-relayer` file, when the variable is set - cleans up related test code. -
Vercel Release Bot authored
This auto-generated PR updates font data with latest available Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Abhay authored
### Improving Documentation Integrate PixelBin Custom Image Loader for optimized image handling PixelBin is Real-time image transformations with automatic optimization, image URL and storage for efficient image organization ### References - [Resize Doc](https://www.pixelbin.io/docs/transformations/basic/resize/#width-w) - [Optimize Doc]( https://www.pixelbin.io/docs/optimizations/quality/#image-quality-when-delivering) ### Contributors - @pnutmath - @umesh162 Co-authored-by:
Steven <steven@ceriously.com>
-
JJ Kasper authored
Looks like we have a syntax error in https://github.com/vercel/next.js/pull/63568 from missing closing `</PagessOnly>` tag. ```sh b383-75ab3d452c93.mdx:0:0: ERROR: [plugin: @mdx-js/esbuild] Expected a closing tag for `</PagesOnly>` (503:1-503:12) ``` x-ref: https://github.com/vercel/next.js/pull/63568 Closes NEXT-3111
-
Ryota Murakami authored
Here are the release notes for pnpm versions v8.15.2 through v8.15.7, - [v8.15.2 Release Notes](https://github.com/pnpm/pnpm/releases/tag/v8.15.2) - [v8.15.3 Release Notes](https://github.com/pnpm/pnpm/releases/tag/v8.15.3) - [v8.15.4 Release Notes](https://github.com/pnpm/pnpm/releases/tag/v8.15.4) - [v8.15.5 Release Notes](https://github.com/pnpm/pnpm/releases/tag/v8.15.5) - [v8.15.6 Release Notes](https://github.com/pnpm/pnpm/releases/tag/v8.15.6) - [v8.15.7 Release Notes](https://github.com/pnpm/pnpm/releases/tag/v8.15.7)
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? There is a race condition in the `pull-build-cache` script. When the remote cache entry was removed between the dry run and the real run, it will run the command and caches whatever is in the native folder. Seems like there are some very old leftover files there which lead to an broken publish. This changes the command to fail when there are no files and empties the folder before running the script. This should lead to pull-build-cache to failing instead. Closes PACK-2957 Fixes #64468
-
- 14 Apr, 2024 3 commits
-
-
vercel-release-bot authored
-
Jiachi Liu authored
### What Inherit the client boudaries from the found matched target in load barrel ### Why The root cause with the barrel transform, we missed the client boundary directive during the transform. Since the new version of mui's case looks like this: Import path page.js (server module) -> `<module>/index.js` (shared module) -> `<module/subpath>/index.js` (client module) -> `<module/subpath/sub-module.js> (client module) After our transform, we lost the `"use client"` which causes the mismatch of the transform: In `rsc` layer: the file pointing to the sub module entry (`<module/subpath>/index.js`), but without the client boundary. Fixes #64369 Closes NEXT-3101
-
Lee Robinson authored
Closes https://github.com/vercel/feedback/issues/61864
-
- 13 Apr, 2024 8 commits
-
-
vercel-release-bot authored
-
Michael Novotny authored
Co-authored-by:
Lee Robinson <me@leerob.io> Co-authored-by:
Ethan Arrowood <ethan@arrowood.dev>
-
Zack Tanner authored
Since the router processes events sequentially, we special case `ACTION_NAVIGATE` events to "discard" a pending server action so that it can process the navigation with higher priority. We should apply this same logic to `ACTION_RESTORE` events (e.g. `router.back()`) for the same reason. Fixes #64432 Closes NEXT-3098
-
Zack Tanner authored
`fetchCache` is a more fine-grained segment level cache-control configuration that most people shouldn't have to use. Current semantics of `dynamic = "force-dynamic"` will still treat the fetch as cacheable unless explicitly overriding it in the fetch, or setting a segment level `fetchCache`. The `dynamic` cache configuration should be seen as a "top-level" configuration, while more fine-grained controls should inherit logical defaults from the top-level. Otherwise this forces people to opt-into the `fetchCache` configuration, or manually override each `fetch` call, which isn't what you'd expect when forcing a segment to be dynamic. This will default to not attempting to cache the fetch when `force-dynamic` is used. As a result, I had to update one of the `app-static` tests to use `revalidate: 0` rather than `force-dynamic`, as the revalidate behavior is slightly different in that it won't modify the revalidation time on a fetch if it's non-zero. Closes NEXT-2067
-
Zack Tanner authored
Looks like the `useTempDir` function throws when running in Azure rather than piping the message to stderr. This makes the test resilient to both cases. <!-- 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 # --> Closes NEXT-3095
-
kxlow authored
The current documentation displays the docs for the `compress` option instead of the `optimizePackageImports` option. https://nextjs.org/docs/pages/api-reference/next-config-js/optimizePackageImports
-
Jiachi Liu authored
The fix is not correct, we already have request ALS wrapping the request in app-render, shouldn't get another one for edge adapter. This is actually a bundler bug Reverts vercel/next.js#64382 Closes NEXT-3097
-
Hung Doan authored
## Why? When you do, → ``` const router = useRouter() console.log('[test] router =', router.query.slug) ``` the value of `router.query.slug` should be undefined in this instance. (screenshot from current docs)  it should be `slug: undefined`.
-
- 12 Apr, 2024 2 commits
-
-
vercel-release-bot authored
-
Colton Ehrman authored
fix(next-lint): update option --report-unused-disable-directives to --report-unused-disable-directives-severity (#64405) ## Why? The Option name and type has been incorrect for `--report-unused-disable-directives` (it's likely that https://github.com/vercel/next.js/pull/61877 exposed this. For correctness, we have updated the name to `--report-unsed-disable-directives-severity` → https://eslint.org/docs/v8.x/use/command-line-interface#--report-unused-disable-directives-severity. - Fixes https://github.com/vercel/next.js/issues/64402 --------- Co-authored-by:
samcx <sam@vercel.com>
-