- 21 Feb, 2025 22 commits
-
-
vercel-release-bot authored
-
Sebastian "Sebbie" Silbermann authored
-
wangsijie authored
### What? Add [Logto](https://logto.io) to the auth libraries list. ### Why? Logto has official Next.js SDK with a well documented quick start guide. Logto is an open-source Auth0 alternative for modern apps and SaaS products, supporting OIDC, OAuth 2.0 and SAML open standards for authentication and authorization. ### How? Co-authored-by:
Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
Zack Tanner authored
This looks like leftover code from when we were running a multi-process architecture.
-
Jiachi Liu authored
-
Sebastian "Sebbie" Silbermann authored
-
JJ Kasper authored
This aims to alleviate an npx cache issue occurring causing datadog script to fail to execute with `'datadog-ci' is not recognized as an internal or external command` x-ref: https://github.com/vercel/next.js/actions/runs/13455042696/job/37598937307#step:36:44
-
Andrew Clark authored
This null check was added as an incidental change in #75981 but I'm not convinced it's actually necessary. Even if it is, it needs to be fixed in the caller, because it means the type is incorrect. I have a suspicion that it was added before the fix to `useMergedRef` landed here: https://github.com/vercel/next.js/pull/75088 If it turns out that this argument is still sometimes `null`, it suggests that there's a bug in `useMergedRef` and we need to fix it there.
-
vercel-release-bot authored
-
Tobias Koppers authored
### What Use a statistical calculation to determine if it's worth to merge chunks or not. And prioritize by that.
-
Tobias Koppers authored
### What? Instead of not looking for further merge candiates when the min chunk size has reached, continue to merge with small chunks that are in all of these chunk groups.
-
Jiachi Liu authored
-
Tobias Koppers authored
### What? only merge small chunks when they occur in multiple overlapping chunk groups. All unmergable small chunks will go into a leftover chunk which combines all non-shared chunks.
-
Zack Tanner authored
-
Vercel Release Bot authored
-
Tobias Koppers authored
### What? Instead of merging the smallest chunks to get over the min chunk size, choose chunks with the biggest overlap in chunk groups to merge. This makes it more likely to have these merged chunks to be shared between chunk groups.
-
Jiwon Choi authored
- Moved source files from `_experimental/` to `ui/`. - Moved `dev-indicators` sources out of `internal/`. - Renamed files and variables to have explicit `app-`, `App`, `pages-` or `Pages` prefixes for better distinguish. - Updated snapshots that were caused by the name change. - Added better type to `next-runtime.webpack-config.js`. - Moved `font/` out of `ui/`. --------- Co-authored-by:
Jiachi Liu <inbox@huozhi.im> Co-authored-by:
Jimmy Lai <laijimmy0@gmail.com>
-
강노아 authored
Co-authored-by:Jiachi Liu <inbox@huozhi.im>
-
Jiachi Liu authored
-
Hendrik Liebau authored
-
Niklas Mischkulnig authored
https://github.com/vercel/next.js/pull/75791 made the sourcemap handling stricter, it caused this when encountering invalid input source maps (i.e. the ones that are published to npm). Let's keep the old behavior for now (which is also what Webpack does). ``` Caused by: 0: Execution of run_inner_operation failed 1: Execution of run_test_operation failed 2: Execution of ModuleGraph::from_modules failed 3: Execution of SingleModuleGraph::new_with_entries failed 4: [project]/turbopack/crates/turbopack-tests/tests/snapshot/source_maps/invalid/input/index.js [test] (ecmascript) 5: Execution of primary_chunkable_referenced_modules failed 6: Execution of <EcmascriptModuleAsset as Module>::references failed 7: Execution of analyse_ecmascript_module failed 8: failed to analyse ecmascript module '[project]/turbopack/crates/turbopack-tests/tests/snapshot/source_maps/invalid/input/index.js [test] (ecmascript)' 9: Execution of <SourceMapReference as GenerateSourceMap>::generate_source_map failed 10: invalid type: string "use client", expected struct SourceMapJson at line 1 column 12 ```
-
Jiachi Liu authored
-
- 20 Feb, 2025 18 commits
-
-
Sam Ko authored
## Why? We should also clarify that the exact subdomain must be specified when using wildcard domains. - Fixes https://github.com/vercel/next.js/issues/76275
-
vercel-release-bot authored
-
Jude Gao authored
When the error message exceeds 200px in height, we want to collapse the part above 200px, and show a button to expand it. [CleanShot 2025-02-20 at 16.46.16.mp4 <span class="graphite__hidden">(uploaded via Graphite)</span> <img class="graphite__hidden" src="https://app.graphite.dev/api/v1/graphite/video/thumbnail/rKSEEwxbNzdFs9t0yyxN/ad657511-2c09-4180-85db-be7325f45d2f.mp4" />](https://app.graphite.dev/media/video/rKSEEwxbNzdFs9t0yyxN/ad657511-2c09-4180-85db-be7325f45d2f.mp4) Closes NDX-743
-
Sam Ko authored
## Why? Follow up to https://github.com/vercel/next.js/pull/75678#discussion_r1964355401.
-
JJ Kasper authored
This vendored packaged is no longer needed as we removed the last usage of it. x-ref: https://github.com/vercel/next.js/pull/75741
-
Hendrik Liebau authored
[flakiness metric](https://app.datadoghq.com/ci/test/runs?query=test_level%3Atest%20env%3Aci%20%40git.repository.id%3Agithub.com%2Fvercel%2Fnext.js%20%40test.service%3Anextjs%20%40test.status%3Afail%20%40test.name%3A%2Appr-full%2A%20%28-%40git.branch%3A%2A%3F%2A%20OR%20%40git.branch%3Acanary%29&agg_m=count&agg_m_source=base&agg_t=count&citest_explorer_sort=timestamp%2Casc&cols=%40test.status%2Ctimestamp%2C%40test.suite%3A83%2C%40test.name%3A607%2C%40git.branch¤tTab=overview&eventStack=&fromUser=false&graphType=flamegraph&index=citest&start=1737457116609&end=1740049116609&paused=false) This attempts to fix the flakiness of two things in the `ppr-full` test suite (there might be more): - Omit tests that rely on a route shell being cached from deploy tests, similar to #72428. - Increase revalidate times from 60 to 120 to avoid the headers tests from receiving a `STALE` response instead of the expected `HIT` response.
-
Zack Tanner authored
When you forget to export a component in the layout, the error message points you to the page component, which is confusing. This ensures the error points to the module that's missing the export. Closes NDX-874
-
Jiachi Liu authored
-
JJ Kasper authored
This ensures we apply the middleware layer when in the node runtime so that `server-only` imports are properly handled. Also ensures our test suite includes this condition for `edge` and `node` runtimes. Fixes: https://github.com/vercel/next.js/issues/75904
-
Sam Ko authored
## Why? We should also have an error page when somebody gets this error → https://github.com/vercel/next.js/blob/d70cac3eb4dee1d1361629d1b4c765365f184e26/packages/next/src/server/app-render/action-handler.ts#L1086.
-
conico974 authored
### What? Using top level await with a node middleware will crash with `adapterFn` is not a function ### Why? When using top level await requiring `middleware.js` will return a promise that need to be awaited ### How? Await the require and changed `getMiddleware` signature Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
JJ Kasper authored
This matches our PPR warning for node middleware while we experiment/validate it further.
-
JJ Kasper authored
This attempts to resolve turbo global failing to install sometimes which current hypothesis is that the turbo process is still running preventing the directory from being wiped/written to. x-ref: [slack thread](https://vercel.slack.com/archives/C04KC8A53T7/p1740004625721209) x-ref: https://github.com/vercel/next.js/actions/runs/13423189899/job/37500545320?pr=76239
-
Jiachi Liu authored
-
Jude Gao authored
We [inject a style tag](https://github.com/vercel/next.js/pull/76225) that downloads Geist fonts from local file system. However, that style tag is injected to the main DOM because of an [issue](https://issues.chromium.org/issues/41085401) in Chrome that the fonts do not work in shadow DOM. We worry that this injected style would interfere with user's styles, or vice versa. Hence, we are going to name them with unique prefix to avoid most collision.
-
Jiwon Choi authored
Following up on #76256, DCE! Saves ~750KB on `dist/` :)  Closes NDX-870
-
Zack Tanner authored
Currently the code frame/terminal headers are treated as a clickable region to open in your editor. However, the editor integration might not always work or be desired, and folks might instead want to copy the file path for other reasons. This moves the "open in editor" functionality to be a specific click area around the icon, removing interactivity from the header & call stack frames. https://github.com/user-attachments/assets/e7e1c282-233f-4ca1-9668-f520f0b7bbe8 Closes NDX-794 Closes NDX-802 --------- Co-authored-by:
devjiwonchoi <devjiwonchoi@gmail.com>
-
Will Binns-Smith authored
When asking the user to open a new issue, link to the new issue form with the bug report template pre-selected.
-