- 25 May, 2023 16 commits
-
-
vercel-release-bot authored
-
vercel-release-bot authored
-
조상현 authored
Co-authored-by:Steven <229881+styfle@users.noreply.github.com>
-
vercel-release-bot authored
-
Shu Ding authored
The React Server Component transform of SWC shouldn't be enabled for files that are not part of "app layers", for example middleware.
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? * remove allowlist * add script to print enabled test cases * enable test suites that turbopack is newly passing
-
Shu Ding authored
If using Server Actions on the client layer without enabling the `serverActions` feature, the build should error. Add a test case to ensure #50199 works.
-
Jiachi Liu authored
Fixes #50312 fix NEXT-1235
-
Tobias Koppers authored
follow up for #50259 --------- Co-authored-by:Justin Ridgewell <justin@ridgewell.name>
-
Tobias Koppers authored
### What? Parallel jobs ### Why? Timeouts otherwise Co-authored-by:JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
JJ Kasper authored
`default` isn't a valid `region` at this point so this removes that. Fixes: https://github.com/vercel/next.js/actions/runs/5076047750/jobs/9118043860#step:6:469
-
vercel-release-bot authored
-
JJ Kasper authored
Lands https://github.com/vercel/next.js/pull/50060 with lint fixes and updated tests. Closes: https://github.com/vercel/next.js/pull/50060 --------- Co-authored-by:
Leah Lundqvist <leah@pigeon.sh>
-
JJ Kasper authored
This ensures we properly normalize app pages in the `web-server` so that it doesn't fail to match/interpolate properly. Fixes: https://github.com/vercel/next.js/issues/43384
-
Justin Ridgewell authored
This change allows the Turbopack's node router to serve `_next/static/development/_devMiddlewareManifest.json` file, which is just the matchers for middleware routes. This is usually handled by the node dev server anyways, but we were filtering out the route so that Turbopack could handle it. But, Turbopack doesn't implement the route matching logic at all, it's all handled by our node router. So Turbopack can't know what the middleware matchers are. Having the router just handle this like the normal dev server is both easy and efficient (I don't want to spin up _another_ node instance just to transform the matchers into the expected format). Fixes WEB-979 --------- Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
- 24 May, 2023 15 commits
-
-
Jiachi Liu authored
* For edge runtime, map `next/server` to esm assets to get benefit from tree-shaking * Mark process.turbo flag as `false` when running with webpack Closes NEXT-1212 Compare with canary (13.4.4-canary.8) #### Middleware ##### before vs after <img width="319" alt="image" src="https://github.com/vercel/next.js/assets/4800338/ffa3e744-8f14-4c61-9f5a-ccd04b8911f2"> <img width="317" alt="image" src="https://github.com/vercel/next.js/assets/4800338/fc974a39-49f3-439a-966c-07af3c71db05"> #### Edge route ##### before vs after <img width="313" alt="image" src="https://github.com/vercel/next.js/assets/4800338/bea6e7bb-5875-4a6b-899f-94ad6a8df902"> <img width="314" alt="image" src="https://github.com/vercel/next.js/assets/4800338/1783fb03-b473-496a-bb97-fa613fe58d7a">
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? Push sass into the css pipeline
-
Maia Teegarden authored
A previous [PR](https://github.com/vercel/next.js/pull/49110#discussion_r1183282878) tried to reuse `rawNextConfig.experimental.outputFileTracingRoot` before invoking Turbopack, but that will always be undefined because `assignDefaults` hasn't been called yet. This creates a shared utility to be reused.
-
JJ Kasper authored
As discussed this includes arguments passed to `unstable_cache` to cacheKey automatically so users don't have to remember to do this manually.
-
JJ Kasper authored
Follow-up to https://github.com/vercel/next.js/pull/50293 we can now avoid this normalizing which isn't as reliable as being able to rely on `localhost` directly since we can't assume it maps to `127.0.0.1` always. x-ref: https://github.com/vercel/next.js/actions/runs/5072034311/jobs/9109241689
-
JJ Kasper authored
Fixes next start listening as it currently behaves in-consistently between dev and start, this shouldn't break any existing behavior as the default is to listen on all interfaces and if it needs to be locked down it still can be. x-ref: https://github.com/vercel/next.js/actions/runs/5065560220/jobs/9094296465
-
Javi Velasco authored
Since there is no longer a limitation that requires us to static analyze `process.env`, this PR removes it from the build process and updates the corresponding documentation.
-
vercel-release-bot authored
-
Shu Ding authored
Previously we are ignoring idents in all var declarators in the check, so it's still possible to fail in some edge cases. CC @kdy1
-
vercel-release-bot authored
-
JJ Kasper authored
Follow-up to https://github.com/vercel/next.js/pull/48019 ensures we don't use arbitrary ports by incrementing favoring always getting a fresh free port instead. Also favors exact address for internal IPC requests instead of `localhost`.
-
JJ Kasper authored
This seems to be failing with the WASM builds so this reverts to allow further investigation x-ref: https://github.com/vercel/next.js/actions/runs/5062818601/jobs/9088828339 x-ref: https://github.com/vercel/next.js/actions/runs/5061364458/jobs/9085596546 x-ref: https://github.com/vercel/next.js/actions/runs/5062868910/jobs/9092170727 Reverts vercel/next.js#49972
-
- 23 May, 2023 9 commits
-
-
vercel-release-bot authored
-
Jiachi Liu authored
A bad alias was introduced in #50128 Fixes #50225
-
Donny/강동윤 authored
### What? Implement a CJS optimizer for next-swc ### Why? x-ref: https://vercel.slack.com/archives/C02HY34AKME/p1684341093462309 Assuming most CJS files are transpiled from ESM, we can mimic tree-shaking using an AST transform. ### How? Closes WEB-1072 Fixes #48469 fix NEXT-1156 --------- Co-authored-by:
Shu Ding <g@shud.in>
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? Enable more test cases to run with turbopack ### Why? These test suites are passing and are not flaky.
-
Cowboy Ho authored
## Bug This fix closes #47083 issue This fix closes #47561 issue This fix closes #48376 issue **Invalid repetition PRs:** #47671 (this PR changing expired code) (This issue still exist on [v13.4.3-canary.1](https://github.com/vercel/next.js/releases/tag/v13.4.3-canary.1) - [x] Related issues linked using `fixes #number` ### What? When running `NODE_OPTIONS='--inspect' next dev`, the render server didn't start with `--inspect`. In some cases, the `--inspect` flag will be passed when `__NEXT_DISABLE_MEMORY_WATCHER` was set. ### Why? Since #47208 revamped some startup processes, the `NODE_OPTIONS` environment parameter is not passed down to the render server worker. ### How? Just add back the original startup process.  link NEXT-1176 --------- Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
Maia Teegarden authored
My computer ignored the casing change when copying things over, which causes resolution errors.
-
Shu Ding authored
This PR adds generated type definitions for `Link` hrefs with only search, hash or with a protocol. Closes #49825. fix NEXT-1203
-
Tobias Koppers authored
### What? align output path of turbopack and webpack ### Why? passing test cases ### Turbopack Changes * https://github.com/vercel/turbo/pull/5072 <!-- Tobias Koppers - improve asset path -->
-