- 13 Jun, 2023 4 commits
-
-
vercel-release-bot authored
-
Kiko Beats authored
Added missing APIs, also sorted all of them alphabetically to make it easier to read. --------- Co-authored-by:Delba de Oliveira <delbabrown@gmail.com>
-
Jiachi Liu authored
Fix prettier lint errors in #51080
-
Michael Novotny authored
* Changes all `Note` → `Good to know` * Consistently puts the colon on the outside of bold text * Documents singe and multi-line styles in contribution guide --------- Co-authored-by:Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
-
- 12 Jun, 2023 27 commits
-
-
vercel-release-bot authored
-
Tyler Lutz authored
-
Max Leiter authored
Improves the documentation to correctly mention that only favicon is restricted to the root app/ segment. x-ref: [slack](https://vercel.slack.com/archives/C03KAR5DCKC/p1686425241975119)
-
Jeremy Douglas Hoover authored
-
Jack Sutton authored
-
Tyler Lutz authored
-
S. Mahdi Mir-Ismaili authored
The sample output of `metadataBase` configuration (`<head <link rel="alternate" ...>`) had an incorrect `href`: https://nextjs.org/docs/app/api-reference/functions/generate-metadata#metadatabase
-
Jiachi Liu authored
Fixes #50232 Passing down the private env into `'render-server'` module to pick up the proper react with require-hook in standalone server fix NEXT-1260
-
Jiachi Liu authored
Fix a missing case from #50970 When navigating from app to page, the `_rsc` query should still be stripped
-
Steven authored
We already have a warning when using `next export` with `output: export` because the `next export` is effectively a no-op (the exported output was already generated during `next build`). However, this PR ensures that `next export -o <dir>` throws an error when `output: export` is defined because the files were already emitted to the `distDir` in the `next build` step and we can't safely no-op at this point. We also guide the user to the correct solution which is to use `output: export` along with `distDir: <dir>` in your next.config.js (instead of mixing legacy behavior with the new behavior). fix #48207 fix NEXT-980
-
Shu Ding authored
Reverts vercel/next.js#51103
-
Delba de Oliveira authored
Fixes https://github.com/vercel/next.js/issues/50844
-
Michael Novotny authored
There was mismatched usage of `js`, `jsx`, `ts`, and `tsx`. Just tried to get them all in sync.
-
Delba de Oliveira authored
Co-authored-by:Michael Novotny <446260+manovotny@users.noreply.github.com>
-
Jiachi Liu authored
Follow up for #50548 There're some packages like `aws-sdk-js-v3` which doesn't have a exports field yet: ``` "main": "./dist-cjs/index.js", "types": "./dist-types/index.d.ts", "module": "./dist-es/index.js", ``` This PR let u pick up by the js assets based on main fields, will prefer `"module"` field instead of `"main"` Closes NEXT-1286
-
OJ Kwon authored
### What? WEB-1150. This PR is an attempt to upload next.js's test results into datadog test trace to track its status. Originally it tried to use automatic trace injection (dd-trace/ci/init). However, due to some of custom environments / setup we use it was not compatible out of the box. Instead, this PR injects a new test reportert to generate junit report, then upload it at once at the end of the testing pipeline. The reporter is configured to run when necessary variables set, local run should not be affected. One thing to note is this report will not count retry results, as it'll create duplicated test entry with multiple results since we runts jest per individual test. This'll allow to detect flaky test easier, but also it means we'll get bit of skewed test results compare to the real world as first failure will be accounted as test fail immediately.
-
Jiachi Liu authored
-
Mehran Mirshekaran authored
-
Shu Ding authored
Add a `NEXT_CPU_PROF` environment variable to programmatically profile CPU for the router worker and two render workers. This is helpful because the `--cpu-prof` isn't reliably writing the result (#27406) especially with our multi-process architecture. 
-
Lee Robinson authored
Using client components for `usePathname` is not a de-optimization. This update tries to make this more clear by sharing more information about the design and tradeoffs of this approach. --------- Co-authored-by:Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
-
Lee Robinson authored
Adds more clarity on which pieces are Next.js only, how actions integrate with Next.js, and details on the progressive enhancement story.
-
Tobias Koppers authored
### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
Tristan authored
-
James Pearson authored
-
Omar Houmz authored
Update next-image-unconfigured-host.md with correct Remote Patterns Documentation link to new docs (#49750)
-
vercel-release-bot authored
-
Jiachi Liu authored
Adding a `_rsc` query for RSC payload requests so that they can be differentiated on resources level for CDN cache for the ones that didn't fully respect to VARY header. Also stripped them for node/edge servers so that they won't show up in the url x-ref: https://github.com/vercel/next.js/pull/49140#issuecomment-1549405009 Closes #49140 Closes NEXT-1268
-
- 11 Jun, 2023 3 commits
-
-
Sayyed Shozib Abbas authored
-
Shu Ding authored
This is a temporary fix before we can ship #51018 (more details there). If there're multiple chunk groups holding the same CSS module, we use files from the first one. This has some flaws but still better than our current status.
-
OJ Kwon authored
### What? context: https://github.com/vercel/next.js/actions/runs/5231928600/jobs/9446394605#step:16:33 For some reason, installing datadog cli on some action runner (Windows) is unexpectedly slow: while other platform takes ~30s, windows only takes more than > 7m. PR updates workflow logic to consolidate artifacts, and then send metrics at once on a separate ubuntu workflow.
-
- 10 Jun, 2023 6 commits
-
-
Jiachi Liu authored
Fixes #51086 The path is used as href, should be normalized as posix style fix NEXT-1282
-
JJ Kasper authored
Small fix ensuring we use the correct repo for getting the last stable tag
-
vercel-release-bot authored
-
vercel-release-bot authored
-
JJ Kasper authored
We publish multiple packages in parallel which can cause issues with the prepublish only script running as turbo clearing/restoring dist caches can causing files to be missing if a publish is in progress. We also don't need to run these as all packages are already built prior to publishing. This also includes fixes for release stats.
-
Shu Ding authored
This review comment was sent after merging the PR: https://github.com/vercel/next.js/pull/51067#discussion_r1224745071 The layer condition doesn't do anything if `hasServerComponents` is disabled.
-