- 07 Mar, 2024 19 commits
-
-
vercel-release-bot authored
-
OJ Kwon authored
### What? Currently wasm binding cannot build lightningcss, until we can make it work falls back to normal css if lightningcss is enabled + wasm bindings are loaded. Closes PACK-2678
-
OJ Kwon authored
### What Looks like we allow d.ts to be included in `match_js_extension`, so if custom rules have an ecmatransform it could raise an error with d.ts. This doesn't make test passes yet, seems there are other issues need to be resolved. Closes PACK-2653
-
OJ Kwon authored
### What? When we write path for the og metadata, basePath was omitted regardless of config. (Actual asset emission was correct, just writing the path in the metadata route) PR updates template code to use config's basePath if exists. Closes PACK-2655
-
Delba de Oliveira authored
-
Delba de Oliveira authored
As per @SukkaW's feedback. Closes: https://linear.app/vercel/issue/DX-2379/clarify-abortcontrollersignal-usage-in-react-fetch-memoization
-
lhfmartin authored
### What? Missing comma to separate dict entries Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Tobias Koppers authored
### Why? Sometimes the turbo build-native command takes longer to restore stealing time from the actual test job Closes PACK-2681
-
Delba de Oliveira authored
Clarify that fetch is not cached when used in a Server Action (see https://github.com/vercel/next.js/pull/60170), and in `POST` requests in Route Handlers.
-
Arian authored
### Adding or Updating Examples Migrate the basic-css example from page router to app router. If it needs further updates, Please let me know Happy to contribute --------- Co-authored-by:Steven <steven@ceriously.com>
-
Vercel Release Bot authored
This auto-generated PR updates the integration test manifest used when testing Turbopack.
-
Donny/강동윤 authored
# Turbopack * https://github.com/vercel/turbo/pull/7625 <!-- Tobias Koppers - generate calls of bindings correctly without this context --> * https://github.com/vercel/turbo/pull/7621 <!-- Donny/강동윤 - fix: Fix purity lint for CSS Modules in swc mode --> * https://github.com/vercel/turbo/pull/7640 <!-- Tobias Koppers - very dynamic requests will only lead to a warning --> * https://github.com/vercel/turbo/pull/7639 <!-- Donny/강동윤 - build: Update `swc_core` to `v0.90.17` --> ### What? Update turbopack ### Why? To keep in sync ### How?
-
Jiachi Liu authored
### What * Move missing html tags error into error overlay, from outside we don't have to manually determine when to render a dummy component with runtime missing tag error or error overlay. * Add brackets `<>` to the html tags in the error  ### Why In #62815, we're having throwing an missing required error, this will trigger another runtime error. Then when error overlay caught it through error event listener, it will render it as an unhandled runtime error: You will see the below message in the overlay. ``` Unhandled Runtime Error Error: The following tas are missing... [Error stack] ``` This error message will bring a message that the error is happened on client during runtime, but actually we already know that is a user side mistake which doesn't have a error trace. This couldn't hmr as you fix the error as well. This PR moves the rendering into error overlay that we're aware of the errors and can render the correct html on client, with the `html` tag attached with error id and `body` wrapping the error overlay. We tell overlay that there're missing tags through props, let it handle everything inside. It can also hmr once you fix the error. One drawback is that when you re-introduce the error, it might trigger react DOM updates exception (`Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.`) instead of the "missing tags" message again. Besides that the HMR works properly. Closes NEXT-2741
-
Balázs Orbán authored
-
Arian authored
Update pnpm version from 8.15.1 to 8.15.4 pnpm 8.15.4 release note https://github.com/pnpm/pnpm/releases/tag/v8.15.4 Previous comment form reviewer https://github.com/vercel/next.js/pull/62963#issuecomment-1982010314
-
Donny/강동윤 authored
### What? Update SWC crates. ### Why? To keep in sync. ### How? Closes PACK-2670
-
Zack Tanner authored
No change in behavior -- this PR updates `applyFlightData` and its recursive functions to receive the prefetch entry rather than a boolean. We only use the actual prefetch entry in `fillLazyItemsTillLeafWithHead` but I found kept getting confused about what this argument was needed for when it was provided so far away from the part where we read the boolean. <!-- 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-2556
-
JJ Kasper authored
This avoids the need to manually check when these get out of sync by having an automated check to keep them in sync when one or the other is updated. x-ref: https://github.com/vercel/next.js/pull/62966 Closes NEXT-2734
-
Balázs Orbán authored
I noticed in #62965 that these were out-of-sync. Content should match: https://github.com/vercel/next.js/blob/canary/packages/next/src/lib/server-external-packages.json Also sorted alphabetically. Closes NEXT-2732
-
- 06 Mar, 2024 21 commits
-
-
James Mikrut authored
Payload is moving to ESM, and we need to be removed from the default list of `serverComponentsExternalPackages`. This PR simply removes Payload from the default list. Developers can add it back in if they are using older versions of Payload. --------- Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
vercel-release-bot authored
-
Sam Ko authored
## Changes - We need to document how that we retry until a port is found when we're not specifying a port via the CLI (`--port`) or the `PORT` environment variable. For example, if `3000` and `3001` are used, we will check `3000`, `3001`, and then land on `3002`. Closes NEXT-2731
-
Eleni Stavropoulou authored
Closes https://github.com/vercel/next.js/issues/62947 This PR fixes the TS Type from the function sitemap. Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
Sam Ko authored
## Why? We need to be up-to-date with this package so our `next/font` is working optimally. → https://github.com/seek-oss/capsize/releases. Unlikely related to the latest [comment](https://github.com/vercel/next.js/issues/47115#issuecomment-1979248754), but a good reminder I need to check this regularly (or we should automate it, or have a better solution). Closes NEXT-2715
-
vercel-release-bot authored
-
JJ Kasper authored
This upgrades to the latest edge-runtime packages as it includes exposing `performance`. This was reverted previously as our publishes were failing with a specific change that has since been removed upstream. Closes NEXT-2730
-
KaygNas authored
### Improving Documentation Add missing `await` keyword in code block. Co-authored-by:Sam Ko <sam@vercel.com>
-
JJ Kasper authored
-
Ethan Arrowood authored
The `encode-decode.ts` file is completely replaceable with the [`TextDecoderStream`](https://developer.mozilla.org/en-US/docs/Web/API/TextDecoderStream) api, but also we can simplify the `streamToString` function too. Working on some benchmarks now - wanted to get CI running to see if this breaks anything though.
-
Sukka authored
The PR adds the new `polyfill.io` instance endpoint (from Fastly and Cloudflare) to the `eslint-plugin-next`'s `no-unwanted-polyfillio` rules, so these new endpoints can be detected by the rule. --- `polyfill.io` was acquired by **a China-based CDN company** "Funnull", see [the announcement from the `polyfill.io` domain owner's Twitter](https://x.com/JakeDChampion/status/1761315227008643367) and https://github.com/polyfillpolyfill/polyfill-service/issues/2834. Despite Funnull's claims of operating in the United States, the predominance of Simplified Chinese on its website suggests otherwise, and it turns out that **"Funnull" is notorious for providing service for the betting and pornography industries**. [The original creator of the `polyfill.io` has voiced his concern on Twitter](https://twitter.com/triblondon/status/1761852117579427975). And since the acquisition, numerous issues have emerged (https://github.com/polyfillpolyfill/polyfill-service/issues/2835, https://github.com/polyfillpolyfill/polyfill-service/issues/2838, https://github.com/alist-org/alist/issues/6100), rendering the `polyfill.io` service **extremely unstable**. Since then, Fastly ([Announcement](https://community.fastly.com/t/new-options-for-polyfill-io-users/2540)) and Cloudflare ([Announcement](https://blog.cloudflare.com/polyfill-io-now-available-on-cdnjs-reduce-your-supply-chain-risk)) has hosted their own instances of `polyfill.io` service. --------- Co-authored-by:
Steven <steven@ceriously.com>
-
Donny/강동윤 authored
### What? I'm recreating a PR because CI of https://github.com/vercel/next.js/pull/58712 uses `lightningcss@1.14.0` for an unknown reason. Add an opt-in feature to use `lightningcss` instead of webpack css-loader. ### Why? In the name of performance. ### How? This PR is largely based on https://github.com/fz6m/lightningcss-loader by @fz6m. (Thank you for nice work) Closes PACK-1998 Closes PACK-2124 --------- Co-authored-by:
OJ Kwon <1210596+kwonoj@users.noreply.github.com>
-
Balázs Orbán authored
-
Balázs Orbán authored
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? fixup for #62927 Closes PACK-2672
-
Balázs Orbán authored
-
OJ Kwon authored
### What I noticed the font manifest generated by Turbopack was always empty. Debugging showed that the path to the client_root was always incorrect when calculating `get_font_paths_from_root`. And also fixed an issue where for certain paths, the (`/index`) manifest key should contain the original path. Closes PACK-2666
-
Vercel Release Bot authored
This auto-generated PR updates the integration test manifest used when testing Turbopack.
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? Merging css chunks need to account for css order when merging chunks ### Why? Changing the order would break css Closes PACK-2671
-