vercel-release-bot
b2625477c0
v15.0.0-canary.53
2024-07-03 05:25:20 +00:00
Benjamin Woodruff
d19862ad0f
[chore] Update turbopack to turbopack-240703.1 ( #67406 )
...
Tobias Koppers - fix typo (vercel/turbo#8619 )
Benjamin Woodruff - Store aggregate read/execute count statistics
(vercel/turbo#8286 )
Tobias Koppers - box InProgress task state (vercel/turbo#8644 )
Tobias Koppers - Task Edges Set/List (vercel/turbo#8624 )
Benjamin Woodruff - Memory: Use `triomphe::Arc` for `SharedReference`
(vercel/turbo#8622 )
Will Binns-Smith - chore: release npm packages (vercel/turbo#8614 )
Will Binns-Smith - devlow-bench: add git branch and sha to datapoints
(vercel/turbo#8602 )
---
Fixes a `triomphe` package version conflict between turbopack and swc by
bumping it from 0.1.11 to 0.1.13.
2024-07-02 21:45:54 -07:00
Donny/강동윤
e7a06bedae
Update @swc/core npm package to v1.6.6 ( #67379 )
...
### What?
Update `@swc/core` to the latest.
### Why?
To keep in sync.
2024-07-03 09:54:28 +09:00
vercel-release-bot
747a60c311
v15.0.0-canary.52
2024-07-02 23:22:46 +00:00
vercel-release-bot
18c2fa85ab
v15.0.0-canary.51
2024-07-02 13:16:34 +00:00
vercel-release-bot
6795597a50
v15.0.0-canary.50
2024-07-01 23:22:58 +00:00
vercel-release-bot
b9bd23baec
v15.0.0-canary.49
2024-06-29 23:22:57 +00:00
vercel-release-bot
b1eab7fb5e
v15.0.0-canary.48
2024-06-28 23:23:25 +00:00
Sam Ko
e6983b911b
chore: update pnpm to 9.4.0 ( #64945 )
...
## Why?
Notable change of v9 is Corepack is enabled by default.
So we can ensure all package manage/resolved exact same version of pnpm.
- [**v9.0.0**](https://github.com/pnpm/pnpm/releases/tag/v9.0.0 ):
Discontinued support for Node.js v16 and introduced Corepack
compatibility checks. New configuration updates include enabling
`dedupe-injected-deps` and changing the lockfile to version 9, with
better readability and resistance to Git conflicts.
...
- [**v9.4.0**](https://github.com/pnpm/pnpm/releases/tag/v9.4.0 )
- Kudos to @ryota-murakami for the original :pr:! →
https://github.com/vercel/next.js/pull/64854
## Changes
- https://pnpm.io/npmrc#link-workspace-packages defaults to `false` now,
so setting it to `true`
Closes NEXT-3211
2024-06-28 04:41:35 -07:00
Sukka
b2eafbf6b3
refactor: replace glob w/ fast-glob in eslint plugin ( #67261 )
2024-06-28 08:15:35 +00:00
Sam Ko
bdd1d31d57
chore: bump turbo to 2.0.6-canary.0 ( #67270 )
2024-06-28 01:15:22 -07:00
vercel-release-bot
1441a353a9
v15.0.0-canary.47
2024-06-27 23:23:39 +00:00
Josh Goldberg ✨
72a64081b4
feat: enable @typescript-eslint/recommended in create-next-app --typescript ( #52845 )
...
Co-authored-by: eps1lon <sebastian.silbermann@vercel.com>
2024-06-27 09:37:01 +00:00
vercel-release-bot
4b7924b155
v15.0.0-canary.46
2024-06-26 23:23:20 +00:00
hrmny
18b13e04f5
fix(turbopack): add no-op resolveAbsolutePath to browser runtime ( #67215 )
...
### What?
The turbopack browser runtime was throwing an error when trying to
access `import.meta.url`.
Closes PACK-3095
Fixes https://github.com/vercel/next.js/issues/66005
2024-06-26 19:18:33 +00:00
vercel-release-bot
ce6ce9b04b
v15.0.0-canary.45
2024-06-26 14:10:16 +00:00
Tim Neutkens
5999c78a4b
Upgrade Turbopack ( #67209 )
...
* https://github.com/vercel/turbo/pull/8546 <!-- Benjamin Woodruff -
Decrease default scope_stress test size, add env var config -->
* https://github.com/vercel/turbo/pull/8563 <!-- Donny/강동윤 - Update
`swc_core` to `v0.95.4` -->
* https://github.com/vercel/turbo/pull/8556 <!-- Tobias Koppers - avoid
cloning the source code -->
* https://github.com/vercel/turbo/pull/8562 <!-- Will Binns-Smith - HMR:
handle non-Latin characters in text through base64-encoded sourcemaps
-->
* https://github.com/vercel/turbo/pull/8530 <!-- Benjamin Woodruff -
Support turbo tasks inside of `mod` blocks -->
* https://github.com/vercel/turbo/pull/8542 <!-- Benjamin Woodruff -
Handle `#[cfg(...)]` attributes on turbo tasks -->
* https://github.com/vercel/turbo/pull/8529 <!-- Benjamin Woodruff -
Deduplicate persistent task get_function_name logic -->
* https://github.com/vercel/turbo/pull/8547 <!-- Benjamin Woodruff - Add
new ExitHandler API as an alternative to ExitGuard -->
* https://github.com/vercel/turbo/pull/8604 <!-- Benjamin Woodruff -
Delete unused TASK_ID_MAPPING support -->
* https://github.com/vercel/turbo/pull/8605 <!-- Benjamin Woodruff -
Remove nohash-hasher dependency -->
* https://github.com/vercel/turbo/pull/8559 <!-- Tobias Koppers - move
stateful flag into Done state -->
* https://github.com/vercel/turbo/pull/8598 <!-- Tim Neutkens - MDX
support: Ensure development transform is only used in development -->
* https://github.com/vercel/turbo/pull/8557 <!-- Tobias Koppers - reduce
size of task output struct -->
* https://github.com/vercel/turbo/pull/8558 <!-- Tobias Koppers - remove
prepared task type -->
<!-- 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 #
-->
2024-06-26 14:11:23 +02:00
Sebastian Silbermann
a832c91ae4
Make synced react-is version more obvious ( #67189 )
2024-06-26 11:16:47 +02:00
vercel-release-bot
90f564d376
v15.0.0-canary.44
2024-06-25 23:22:44 +00:00
Ivan Torres
0d9c89bf81
Remove devdependency uuid ( #67190 )
...
Co-authored-by: torresgol10.it <torresgol10.itd@gmail.com>
Co-authored-by: eps1lon <sebastian.silbermann@vercel.com>
2024-06-25 20:50:39 +00:00
Jiwon Choi
ebc2c68c4c
chore: upgrade ts to 5.4 ( #67171 )
...
Stepping stone before #67113
Closes NEXT-3136
---------
Co-authored-by: Jiachi Liu <inbox@huozhi.im>
2024-06-25 23:12:28 +09:00
vercel-release-bot
ea8020158e
v15.0.0-canary.43
2024-06-24 23:23:43 +00:00
vercel-release-bot
6604c187ec
v15.0.0-canary.42
2024-06-23 23:22:39 +00:00
Ivan Torres
515836dab0
Bump conf to 13.0.0 ( #67043 )
...
Bump conf to 13.0.0
I have changed the `moduleResolution` in tsconfig to `bundler` because
apparently the new versions of that dependency does not work with
`moduleResolution:node`, issues where it explains it: [issues in
conf](https://github.com/sindresorhus/conf/issues/181 )
---------
Co-authored-by: torresgol10.itd <torresgol10.itd@gmail.com>
Co-authored-by: Sam Ko <sam@vercel.com>
2024-06-23 09:17:38 +00:00
vercel-release-bot
7f0102dcae
v15.0.0-canary.41
2024-06-22 23:22:19 +00:00
vercel-release-bot
a7930c3c29
v15.0.0-canary.40
2024-06-21 23:22:06 +00:00
vercel-release-bot
32992fc0be
v15.0.0-canary.39
2024-06-20 23:23:47 +00:00
Tim Neutkens
b515bbc4bb
Upgrade Turbopack ( #67017 )
...
Upgrades Turbopack
* https://github.com/vercel/turbo/pull/8421 <!-- Tim Neutkens - Fix
Turbopack benchmark for next@canary -->
* https://github.com/vercel/turbo/pull/8396 <!-- Tim Neutkens - Rename
dev_runtime to browser_runtime -->
* https://github.com/vercel/turbo/pull/8397 <!-- Tim Neutkens - Rename
runtime/none to runtime/edge -->
* https://github.com/vercel/turbo/pull/8398 <!-- Tim Neutkens - Remove
unused Node.js runtime -->
* https://github.com/vercel/turbo/pull/8399 <!-- Tim Neutkens - Rename
build runtime to nodejs -->
* https://github.com/vercel/turbo/pull/8400 <!-- Tim Neutkens - Rename
dev runtime to browser -->
<!-- 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 #
-->
2024-06-20 09:26:01 +02:00
vercel-release-bot
16f5c28cb3
v15.0.0-canary.38
2024-06-19 23:23:14 +00:00
Joost
50b9966ba9
Add sassOption implementation to support sass-embedded ( #64577 )
...
## What?
This PR adds an option to use `sass-embedded`.
## Why?
For large projects sass-embedded improves SCSS compilation time by over
50%.
See also https://github.com/vercel/next.js/discussions/36160
## How?
Added a sassOption `implementation` to configure the sass-loader which
Sass implementation to use.
See also https://www.npmjs.com/package/sass-loader#implementation
I think this a similar approach to what is done for `additionalData`.
## Additional notes
In order to support `sass-embedded`, `sass-loader` is upgraded to
12.6.0.
---------
Co-authored-by: Zack Tanner <1939140+ztanner@users.noreply.github.com>
2024-06-19 14:50:21 +00:00
vercel-release-bot
9889322d72
v15.0.0-canary.37
2024-06-18 23:23:07 +00:00
Will Binns-Smith
f30e5dbb29
Run and report benchmarks ( #66851 )
...
Using `@vercel/devlow-bench`, this benchmarks changes landed on canary
and reports results to Datadog.
2024-06-18 11:11:15 -07:00
Donny/강동윤
e931ec671c
build: Update swc_core to v0.95.2 ( #66902 )
...
# Turbopack
* https://github.com/vercel/turbo/pull/8473 <!-- Donny/강동윤 - feat: Check
the number of direct dependants while tree shaking -->
* https://github.com/vercel/turbo/pull/8420 <!-- Tobias Koppers - Tree
Shaking grouping of items -->
* https://github.com/vercel/turbo/pull/8510 <!-- Tobias Koppers - read
larger chunks when reading a trace file -->
* https://github.com/vercel/turbo/pull/8509 <!-- Tobias Koppers - avoid
duplicates in primary_modules -->
* https://github.com/vercel/turbo/pull/8508 <!-- Tobias Koppers - only
create spans for nodes that are actually visited -->
* https://github.com/vercel/turbo/pull/8502 <!-- Donny/강동윤 - build:
Update `swc_core` to `v0.95.2` -->
### What?
Update `swc_core`.
- [CHANGELOG](064af5391d/CHANGELOG.md (160---2024-06-15)
2024-06-18 03:27:52 +00:00
vercel-release-bot
83f21e98c5
v15.0.0-canary.36
2024-06-17 23:23:31 +00:00
Ivan Torres
a4208200fb
Bump ci-info to 4.0.0 ( #66810 )
...
Bump ci-info to 4.0.0, deleted from devDevpendecy: @types/ci-info , now
the dependency brings the types.
Co-authored-by: torresgol10.itd <torresgol10.itd@gmail.com>
Co-authored-by: Sam Ko <sam@vercel.com>
2024-06-17 00:14:50 -07:00
vercel-release-bot
e07b8b8e15
v15.0.0-canary.35
2024-06-16 23:23:54 +00:00
vercel-release-bot
3dba220b0b
v15.0.0-canary.34
2024-06-15 23:22:41 +00:00
vercel-release-bot
5e30f86bc7
v15.0.0-canary.33
2024-06-15 18:23:39 +00:00
Benjamin Woodruff
0b1209edfa
Revert "Revert "Use turbo-tasks-malloc on all platforms" ( #66884 )", fix aarch64 compilation in CI ( #66885 )
...
We either need GCC >= 4.9 or we need to link with libatomic:
https://github.com/microsoft/mimalloc/issues/443
Unfortunately, manylinux2014-cross ships with GCC 4.8.5:
https://github.com/rust-cross/manylinux-cross/blob/main/manylinux2014/aarch64/Dockerfile#L71
We already appear to override the compiler toolchain in CI for x86_64 to
use clang (which is why mimalloc works there), so let's go ahead and do
that here too. This at least means we're using the same compiler across
both architectures.
I'm leaving the aarch64-musl codepath the same (using gcc) because (1)
we don't use mimalloc there yet and (2) it's a bit harder for me to test
as thoroughly.
# Testing
## Local Compilation
Run bash inside the docker image (I also had to install rosetta2 inside
my Linux VM, as this is an x86_64 image used for cross-compilation to
aarch64):
```
podman run --platform=linux/amd64 -t -i ghcr.io/napi-rs/napi-rs/nodejs-rust:stable-2023-09-17-aarch64 bash -l
```
```
git clone https://github.com/vercel/next.js.git --filter=blob:none --branch canary --single-branch
cd next.js
git checkout 6ae9828ccehttps://github.com/vercel/next.js/actions/runs/9523143080/job/26254016137
2024-06-15 03:39:24 +00:00
vercel-release-bot
d12b7a5d2a
v15.0.0-canary.32
2024-06-14 23:23:00 +00:00
vercel-release-bot
6306ea3c1a
v15.0.0-canary.31
2024-06-14 20:56:05 +00:00
JJ Kasper
fd9c524a72
Revert "Use turbo-tasks-malloc on all platforms" ( #66884 )
...
Reverting while we investigate further
Reverts vercel/next.js#66815
2024-06-14 13:36:19 -07:00
vercel-release-bot
e4d107cc93
v15.0.0-canary.30
2024-06-14 15:05:15 +00:00
Benjamin Woodruff
a00146e001
Use turbo-tasks-malloc on all platforms ( #66815 )
...
This was previously disabled on `aarch64-unknown-linux-musl` and `wasm`,
due to compilation errors.
I moved the logic to disable `mimalloc` on these platforms into the
`turbo-tasks-malloc` crates in https://github.com/vercel/turbo/pull/8462
(which this PR depends on).
In addition to centralizing mimalloc platform support logic, this means
that we can get allocation data from these platforms while using the
system allocator.
**Depends on:** https://github.com/vercel/turbo/pull/8462
Included turbopack changes:
* https://github.com/vercel/turbo/pull/8409 <!-- hrmny -
fix(turbopack-ecmascript-runtime): prevent hanging when top level await
is skipped -->
* https://github.com/vercel/turbo/pull/8466 <!-- hrmny - fix(turbopack):
make external module wrapper return not found instead of panicking -->
* https://github.com/vercel/turbo/pull/8469 <!-- hrmny - fix(turbopack):
add ecmascript options to mdx -->
* https://github.com/vercel/turbo/pull/8447 <!-- Donny/강동윤 - build:
Update `swc_core` to `v0.93.4` -->
* https://github.com/vercel/turbo/pull/8472 <!-- Donny/강동윤 - feat:
Reduce the number of parts created by tree shaking -->
* https://github.com/vercel/turbo/pull/8480 <!-- Will Binns-Smith -
Publish `@vercel/devlow-bench` -->
* https://github.com/vercel/turbo/pull/8481 <!-- Will Binns-Smith -
chore: release npm packages -->
* https://github.com/vercel/turbo/pull/8462 <!-- Benjamin Woodruff -
Update mimalloc, enable for glibc Linux aarch64, explicitly disable for
wasm and musl -->
2024-06-14 04:56:04 +00:00
vercel-release-bot
c0b3c47059
v15.0.0-canary.29
2024-06-14 00:14:19 +00:00
vercel-release-bot
970420d78b
v15.0.0-canary.28
2024-06-12 22:23:29 +00:00
Sam Ko
e296846427
chore: bump turbo to 2.0.3 ( #66784 )
...
## Why?
This pull request bumps turborepo from 1.13.3-canary.2 to
[2.0.3](https://github.com/vercel/turbo/releases/tag/v2.0.3 ) across
multiple GitHub workflows and configuration files.
Re-attempting after we
[reverted](https://github.com/vercel/next.js/pull/66775 ).
2024-06-12 19:31:42 +00:00
Ivan Torres
bebc63fce0
Update devdependecy commander ( #66771 )
...
Upgrade devdependecy commander to latest versio.
Now in command, the optional argument is with [] and the required
argument is with <>.
---------
Co-authored-by: torresgol10.itd <torresgol10.itd@gmail.com>
Co-authored-by: Sam Ko <sam@vercel.com>
2024-06-12 11:25:09 -07:00
Tim Neutkens
f87dc4ae5e
Add bench application with heavy dependencies ( #66564 )
...
## What?
Work in progress, I'm collecting some dependencies that we keep seeing
in traces of slow compilation, makes it easier to optimize these.
<!-- 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 #
-->
2024-06-12 15:05:47 +02:00
Tobias Koppers
4398e348ee
use node js chunking context for evaluation ( #66710 )
...
### What?
Refactoring to use node.js chunking context for evaluation
see https://github.com/vercel/turbo/pull/8402
### Why?
### Turbopack changes
* vercel/turbo#8422
* vercel/turbo#8402
2024-06-12 10:38:28 +00:00
