OJ Kwon
d7f1e4552a
build(cargo): update turbopack for filewatcher fix ( #61955 )
...
<!-- 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 #
-->
### What
* https://github.com/vercel/turbo/pull/7340 <!-- OJ Kwon -
feat(tasks-fs): bump up notify, fix empty file watch -->
Bump up turbopack PR to fix hmr issues.
Closes PACK-2466
2024-02-12 10:41:39 -08:00
vercel-release-bot
6a049eaf0c
v14.1.1-canary.49
2024-02-12 18:11:59 +00:00
OJ Kwon
63f160e8b3
build(cargo): bump up turbopack to latest ( #61952 )
...
### What?
Bump up turbopack to latest. This is to cut off turbopack **before**
including filewatcher changes, so we can easily bisect & revert if
watcher have regressions.
2024-02-12 10:08:40 -08:00
vercel-release-bot
5437fdaa15
v14.1.1-canary.48
2024-02-11 23:22:10 +00:00
vercel-release-bot
03b652a955
v14.1.1-canary.47
2024-02-10 23:21:27 +00:00
vercel-release-bot
194311d8c9
v14.1.1-canary.46
2024-02-09 21:49:06 +00:00
Tobias Koppers
5c74ed9258
update turbopack ( #61187 )
...
### What?
* https://github.com/vercel/turbo/pull/7302 <!-- Tobias Koppers -
support exporting undefined -->
* https://github.com/vercel/turbo/pull/7303 <!-- Tobias Koppers -
improve HMR performance -->
* https://github.com/vercel/turbo/pull/7306 <!-- OJ Kwon - ci(test): add
wasi target check for the supported packages -->
* https://github.com/vercel/turbo/pull/7308 <!-- OJ Kwon - build(cargo):
apply formatting -->
* https://github.com/vercel/turbo/pull/7117 <!-- Tobias Koppers - track
RequestKey during resolving and avoid duplicate keys -->
Closes PACK-2299
2024-02-09 18:57:15 +01:00
vercel-release-bot
f8343210dd
v14.1.1-canary.45
2024-02-09 09:18:47 +00:00
Zack Tanner
f1655147b4
Update React from 2bc7d336a to ba5e6a832 ( #61837 )
...
Updates React from 2bc7d336a to ba5e6a832.
### React upstream changes
- https://github.com/facebook/react/pull/28283
- https://github.com/facebook/react/pull/28280
- https://github.com/facebook/react/pull/28079
- https://github.com/facebook/react/pull/28233
- https://github.com/facebook/react/pull/28276
- https://github.com/facebook/react/pull/28272
- https://github.com/facebook/react/pull/28265
- https://github.com/facebook/react/pull/28259
- https://github.com/facebook/react/pull/28153
- https://github.com/facebook/react/pull/28246
- https://github.com/facebook/react/pull/28218
- https://github.com/facebook/react/pull/28263
- https://github.com/facebook/react/pull/28257
- https://github.com/facebook/react/pull/28261
- https://github.com/facebook/react/pull/28262
- https://github.com/facebook/react/pull/28260
- https://github.com/facebook/react/pull/28258
- https://github.com/facebook/react/pull/27864
- https://github.com/facebook/react/pull/28254
- https://github.com/facebook/react/pull/28219
- https://github.com/facebook/react/pull/28248
- https://github.com/facebook/react/pull/28216
- https://github.com/facebook/react/pull/28249
- https://github.com/facebook/react/pull/28241
- https://github.com/facebook/react/pull/28243
- https://github.com/facebook/react/pull/28253
- https://github.com/facebook/react/pull/28256
- https://github.com/facebook/react/pull/28236
- https://github.com/facebook/react/pull/28237
- https://github.com/facebook/react/pull/28242
- https://github.com/facebook/react/pull/28251
- https://github.com/facebook/react/pull/28252
Closes NEXT-2411
2024-02-09 10:13:45 +01:00
Steven
698fcbb8d1
fix: babel usage with next/image ( #61835 )
...
### Why
The `process/browser` lib was imported and being transformed, but
`process.browser = true` turns to `true = true` that causes the
compilation error, we need to exclude them from certain compilation
layers
### What
- Fixes https://github.com/vercel/next.js/issues/61116
Closes NEXT-2410
Closes NEXT-2328
---------
Co-authored-by: Jiachi Liu <inbox@huozhi.im>
2024-02-08 18:16:30 -05:00
vercel-release-bot
0114c2cb24
v14.1.1-canary.44
2024-02-08 12:22:09 +00:00
Jimmy Lai
feb27ad621
Revert "feat(next/image)!: remove squoosh in favor of sharp as optional dep" ( #61810 )
...
Reverts vercel/next.js#61696
Closes NEXT-2401
2024-02-08 11:00:34 +00:00
vercel-release-bot
d04cfb68a4
v14.1.1-canary.43
2024-02-07 23:21:21 +00:00
vercel-release-bot
fa4d1a501c
v14.1.1-canary.42
2024-02-07 08:48:27 +00:00
Tobias Koppers
86c46edce7
source map fixes ( #61723 )
...
### What?
* show guessed original file for generate code
* avoid internal cast
* add get_source_map method
* hide turbopack runtime stack lines
* hide unmapped stack lines
Closes PACK-2400
Before:
After:
and expanded:
### Other Turbopack changes
* https://github.com/vercel/turbo/pull/4235 <!-- Leah -
chore(turborepo-lib): use compile error for feature validation -->
* https://github.com/vercel/turbo/pull/7285 <!-- Tobias Koppers -
resolve source maps that are attached in source code -->
* https://github.com/vercel/turbo/pull/7301 <!-- Donny/강동윤 -
fix(turbopack): Reverse order of css chunks to fix css module issues -->
* https://github.com/vercel/turbo/pull/7286 <!-- Tobias Koppers - guess
original source for generated code -->
2024-02-07 08:58:08 +01:00
vercel-release-bot
b77373e283
v14.1.1-canary.41
2024-02-07 06:48:49 +00:00
vercel-release-bot
b61a709068
v14.1.1-canary.40
2024-02-06 23:21:25 +00:00
vercel-release-bot
f07c2bd559
v14.1.1-canary.39
2024-02-06 23:19:27 +00:00
vercel-release-bot
300cf76c83
v14.1.1-canary.38
2024-02-06 19:24:56 +00:00
Steven
07c4ec052e
feat(next/image)!: remove squoosh in favor of sharp as optional dep ( #61696 )
...
## History
Previously, we added support for `squoosh` because it was a wasm
implementation that "just worked" on all platforms when running `next
dev` for the first time. However, it was slow so we always recommended
manually installing `sharp` for production use cases running `next
build` and `next start`.
Now that [`sharp` supports
webassembly](https://sharp.pixelplumbing.com/install#webassembly ), we no
longer need to maintain `squoosh`, so it can be removed. We also don't
need to make the user install sharp manually because it can be installed
under `optionalDependencies`. I left it optional in case there was some
platform that still needed to manually install the wasm variant with
`npm install --cpu=wasm32 sharp` such as codesandbox/stackblitz (I don't
believe sharp has any fallback built in yet).
Since we can guarantee `sharp`, we can also remove `get-orientation` dep
and upgrade `image-size` dep.
I also moved an [existing `sharp`
test](https://github.com/vercel/next.js/pull/56674 ) into its own fixture
since it was unrelated to image optimization.
## Related Issues
- Fixes https://github.com/vercel/next.js/issues/41417
- Closes https://github.com/vercel/next.js/pull/54670
- Related https://github.com/vercel/next.js/issues/54708
- Related https://github.com/vercel/next.js/issues/44804
- Related https://github.com/vercel/next.js/issues/48820
2024-02-06 14:17:07 -05:00
OJ Kwon
9cadae5eef
feat(next-swc): support wasm32-* build target ( #61586 )
...
<!-- 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
### How?
Closes NEXT-
Fixes #
-->
### What?
This PR introduces a ground work to generate wasm bindings package from
our napi bindings. This doesn't actually replace anything yet, however
aim to establish our napi bindings package can be built against wasm32
target.
### Why?
We currently have two bindings package to generate native / wasm target
support, one for napi and one other for wasm. Recently napi-rs started
to support to generate bindings for the wasm directly - which means we
can get rid of the wasm-pack based bindings code entirely and maintain a
single bindings code only.
This'll makes our `next-swc` simpler as well, since the invocation to
the bindings now becomes identical we don't have to additional wasm
specific logics to invoke functions (i.e transform, transformsync..).
Also napi generates wasi-supported wasm bindings, provides few more
features to the current wasm bindings.
#### Good
- Async napi binding fn works transparently (`transform`, `minify`...)
- (Experimental) thread supports depends on node.js runtime
- Wasi support: i.e it can even read filesystem directly!
#### Things to consider
- node.js's wasi support is experimental yet
- napi-rs's wasm support is in beta yet, specifically `packaging`
generated wasm output.
Due to `things to consider` reasons, this PR does not replace existing
wasm target yet. We should be able to plan out things later.
**What happens to the turbopack api in napi bindings?**
Simply put, this **does not support turbopack in wasm**. Build works by
disabling turbopack (more notably, underlying dependency doesn't support
wasm) features. It is something to explore separately.
Closes PACK-2367
There is a branch at https://github.com/vercel/next.js/pull/61586 shows
quick demo for importing, running sync / async / read external files.
2024-02-06 10:15:13 -08:00
vercel-release-bot
59bf406d0a
v14.1.1-canary.37
2024-02-06 17:07:44 +00:00
Leah
f910e2bdcd
chore: update turbopack ( #61682 )
...
### Turbopack Updates
* https://github.com/vercel/turbo/pull/7240 <!-- OJ Kwon -
refactor(turbopack): remove deprecated options -->
* https://github.com/vercel/turbo/pull/7241 <!-- Will Binns-Smith -
Turbopack: Fix Next.js in cross-bundler benchmarks -->
* https://github.com/vercel/turbo/pull/7274 <!-- Leah - fix(turbopack):
support reloading typescript tailwind config -->
Fixes #61607
2024-02-06 14:40:15 +01:00
Josh Story
23955574ae
Update React from 60a927d04 to 2bc7d336a ( #61522 )
...
Updates React from 60a927d04 to 2bc7d336a
Also updates aliases for `react.shared-subset` to `react.react-server`
### React upstream changes
- https://github.com/facebook/react/pull/28250
- https://github.com/facebook/react/pull/28225
- https://github.com/facebook/react/pull/28123
- https://github.com/facebook/react/pull/28240
- https://github.com/facebook/react/pull/28239
- https://github.com/facebook/react/pull/28245
- https://github.com/facebook/react/pull/28244
- https://github.com/facebook/react/pull/28238
- https://github.com/facebook/react/pull/28235
- https://github.com/facebook/react/pull/28221
- https://github.com/facebook/react/pull/28215
- https://github.com/facebook/react/pull/28214
- https://github.com/facebook/react/pull/28213
- https://github.com/facebook/react/pull/28212
- https://github.com/facebook/react/pull/28211
- https://github.com/facebook/react/pull/28247
- https://github.com/facebook/react/pull/28210
- https://github.com/facebook/react/pull/28186
- https://github.com/facebook/react/pull/28232
- https://github.com/facebook/react/pull/28169
- https://github.com/facebook/react/pull/28177
- https://github.com/facebook/react/pull/28170
- https://github.com/facebook/react/pull/28168
- https://github.com/facebook/react/pull/28122
- https://github.com/facebook/react/pull/27982
- https://github.com/facebook/react/pull/28217
- https://github.com/facebook/react/pull/28223
- https://github.com/facebook/react/pull/28208
- https://github.com/facebook/react/pull/28209
- https://github.com/facebook/react/pull/28200
- https://github.com/facebook/react/pull/28199
- https://github.com/facebook/react/pull/28198
- https://github.com/facebook/react/pull/28197
- https://github.com/facebook/react/pull/28196
- https://github.com/facebook/react/pull/28194
- https://github.com/facebook/react/pull/28192
- https://github.com/facebook/react/pull/28191
- https://github.com/facebook/react/pull/28182
- https://github.com/facebook/react/pull/28181
- https://github.com/facebook/react/pull/28180
- https://github.com/facebook/react/pull/28178
- https://github.com/facebook/react/pull/28201
- https://github.com/facebook/react/pull/28176
- https://github.com/facebook/react/pull/28162
- https://github.com/facebook/react/pull/28131
- https://github.com/facebook/react/pull/28190
- https://github.com/facebook/react/pull/28172
- https://github.com/facebook/react/pull/28171
- https://github.com/facebook/react/pull/28173
- https://github.com/facebook/react/pull/28174
- https://github.com/facebook/react/pull/28175
- https://github.com/facebook/react/pull/28136
- https://github.com/facebook/react/pull/28135
- https://github.com/facebook/react/pull/28134
- https://github.com/facebook/react/pull/28133
- https://github.com/facebook/react/pull/28132
- https://github.com/facebook/react/pull/28130
- https://github.com/facebook/react/pull/28202
- https://github.com/facebook/react/pull/28102
- https://github.com/facebook/react/pull/28161
- https://github.com/facebook/react/pull/28193
- https://github.com/facebook/react/pull/28195
- https://github.com/facebook/react/pull/28189
- https://github.com/facebook/react/pull/28160
- https://github.com/facebook/react/pull/28096
- https://github.com/facebook/react/pull/28183
- https://github.com/facebook/react/pull/28125
- https://github.com/facebook/react/pull/28157
- https://github.com/facebook/react/pull/28115
- https://github.com/facebook/react/pull/28124
- https://github.com/facebook/react/pull/28163
- https://github.com/facebook/react/pull/28164
- https://github.com/facebook/react/pull/28150
- https://github.com/facebook/react/pull/28159
- https://github.com/facebook/react/pull/28069
- https://github.com/facebook/react/pull/28110
- https://github.com/facebook/react/pull/28148
- https://github.com/facebook/react/pull/28116
- https://github.com/facebook/react/pull/28099
- https://github.com/facebook/react/pull/28100
- https://github.com/facebook/react/pull/28147
- https://github.com/facebook/react/pull/28128
- https://github.com/facebook/react/pull/28126
- https://github.com/facebook/react/pull/28139
- https://github.com/facebook/react/pull/28140
- https://github.com/facebook/react/pull/28141
- https://github.com/facebook/react/pull/28142
- https://github.com/facebook/react/pull/28113
- https://github.com/facebook/react/pull/28129
- https://github.com/facebook/react/pull/28114
- https://github.com/facebook/react/pull/28053
- https://github.com/facebook/react/pull/28091
- https://github.com/facebook/react/pull/28087
- https://github.com/facebook/react/pull/28112
- https://github.com/facebook/react/pull/28086
- https://github.com/facebook/react/pull/28101
- https://github.com/facebook/react/pull/28106
- https://github.com/facebook/react/pull/28117
- https://github.com/facebook/react/pull/28118
- https://github.com/facebook/react/pull/28105
- https://github.com/facebook/react/pull/27883
- https://github.com/facebook/react/pull/28111
- https://github.com/facebook/react/pull/28095
- https://github.com/facebook/react/pull/28108
- https://github.com/facebook/react/pull/28090
- https://github.com/facebook/react/pull/28089
- https://github.com/facebook/react/pull/28076
- https://github.com/facebook/react/pull/28074
- https://github.com/facebook/react/pull/28103
- https://github.com/facebook/react/pull/28098
- https://github.com/facebook/react/pull/28097
- https://github.com/facebook/react/pull/28068
- https://github.com/facebook/react/pull/28093
- https://github.com/facebook/react/pull/28094
- https://github.com/facebook/react/pull/28073
- https://github.com/facebook/react/pull/28084
- https://github.com/facebook/react/pull/28063
- https://github.com/facebook/react/pull/28085
- https://github.com/facebook/react/pull/28083
- https://github.com/facebook/react/pull/28065
- https://github.com/facebook/react/pull/28061
- https://github.com/facebook/react/pull/28077
- https://github.com/facebook/react/pull/28075
- https://github.com/facebook/react/pull/28078
- https://github.com/facebook/react/pull/28050
- https://github.com/facebook/react/pull/28011
- https://github.com/facebook/react/pull/28055
- https://github.com/facebook/react/pull/28066
- https://github.com/facebook/react/pull/28067
- https://github.com/facebook/react/pull/28010
- https://github.com/facebook/react/pull/27993
- https://github.com/facebook/react/pull/28052
- https://github.com/facebook/react/pull/28060
- https://github.com/facebook/react/pull/28059
- https://github.com/facebook/react/pull/28034
- https://github.com/facebook/react/pull/28033
- https://github.com/facebook/react/pull/28004
- https://github.com/facebook/react/pull/28051
- https://github.com/facebook/react/pull/28012
- https://github.com/facebook/react/pull/28001
- https://github.com/facebook/react/pull/28002
- https://github.com/facebook/react/pull/27995
- https://github.com/facebook/react/pull/28006
- https://github.com/facebook/react/pull/28005
- https://github.com/facebook/react/pull/28007
- https://github.com/facebook/react/pull/28008
- https://github.com/facebook/react/pull/28009
- https://github.com/facebook/react/pull/28000
- https://github.com/facebook/react/pull/28003
- https://github.com/facebook/react/pull/27997
- https://github.com/facebook/react/pull/27240
- https://github.com/facebook/react/pull/27977
- https://github.com/facebook/react/pull/27940
- https://github.com/facebook/react/pull/27939
- https://github.com/facebook/react/pull/28090
- https://github.com/facebook/react/pull/28089
- https://github.com/facebook/react/pull/28076
- https://github.com/facebook/react/pull/28074
- https://github.com/facebook/react/pull/28103
- https://github.com/facebook/react/pull/28098
- https://github.com/facebook/react/pull/28097
- https://github.com/facebook/react/pull/28068
- https://github.com/facebook/react/pull/28093
- https://github.com/facebook/react/pull/28094
- https://github.com/facebook/react/pull/28073
- https://github.com/facebook/react/pull/28084
- https://github.com/facebook/react/pull/28063
- https://github.com/facebook/react/pull/28085
- https://github.com/facebook/react/pull/28083
- https://github.com/facebook/react/pull/28065
- https://github.com/facebook/react/pull/28061
- https://github.com/facebook/react/pull/28077
- https://github.com/facebook/react/pull/28075
- https://github.com/facebook/react/pull/28078
- https://github.com/facebook/react/pull/28050
- https://github.com/facebook/react/pull/28011
- https://github.com/facebook/react/pull/28055
- https://github.com/facebook/react/pull/28066
- https://github.com/facebook/react/pull/28067
- https://github.com/facebook/react/pull/28010
- https://github.com/facebook/react/pull/27993
- https://github.com/facebook/react/pull/28052
- https://github.com/facebook/react/pull/28060
- https://github.com/facebook/react/pull/28059
- https://github.com/facebook/react/pull/28034
- https://github.com/facebook/react/pull/28033
- https://github.com/facebook/react/pull/28004
- https://github.com/facebook/react/pull/28051
- https://github.com/facebook/react/pull/28012
- https://github.com/facebook/react/pull/28001
- https://github.com/facebook/react/pull/28002
- https://github.com/facebook/react/pull/27995
- https://github.com/facebook/react/pull/28006
- https://github.com/facebook/react/pull/28005
- https://github.com/facebook/react/pull/28007
- https://github.com/facebook/react/pull/28008
- https://github.com/facebook/react/pull/28009
- https://github.com/facebook/react/pull/28000
- https://github.com/facebook/react/pull/28003
- https://github.com/facebook/react/pull/27997
- https://github.com/facebook/react/pull/27240
- https://github.com/facebook/react/pull/27977
- https://github.com/facebook/react/pull/27940
- https://github.com/facebook/react/pull/27939
Closes NEXT-2331
2024-02-05 18:22:27 -08:00
vercel-release-bot
bdd0dd2d50
v14.1.1-canary.36
2024-02-05 23:22:30 +00:00
vercel-release-bot
b1f6b8246e
v14.1.1-canary.35
2024-02-05 19:38:59 +00:00
JJ Kasper
2ad058d356
Revert "build: upgrade edge-runtime" ( #61686 )
...
See here for additional context
https://github.com/vercel/edge-runtime/pull/795 but TLDR is due to a bug
in the `npmcli` we aren't able to publish Next.js releases after this
package was upgraded.
We can re-land the upgrade after that PR is landed/published.
Reverts vercel/next.js#61030
Closes NEXT-2367
2024-02-05 19:18:08 +00:00
vercel-release-bot
d1fa2876e8
v14.1.1-canary.34
2024-02-05 17:25:07 +00:00
Donny/강동윤
8a11319efb
chore: Update @swc/helpers to v0.5.5 ( #61659 )
...
### What?
Update `@swc/helpers` to `v0.5.5`.
### Why?
- To apply https://github.com/swc-project/swc/pull/8574 . This fixes a bug in helper, which can prevent useful operation while testing with `@next/jest`.
(https://github.com/swc-project/swc/pull/8097 is also included, but it's not used by next.js)
### How?
Closes PACK-2388
2024-02-05 19:22:32 +09:00
vercel-release-bot
5d2e79b61f
v14.1.1-canary.33
2024-02-05 01:29:47 +00:00
Sam Ko
c1bce948e9
chore: upgrade turbo to 1.12.2 ( #61643 )
...
## Changes
- Upgrade turbo from 1.11.3 to 1.12.2
Closes NEXT-2353
2024-02-05 00:03:06 +00:00
vercel-release-bot
498d29413b
v14.1.1-canary.32
2024-02-04 23:21:04 +00:00
JJ Kasper
4a5f5dee3f
Remove extra edge-runtime/primitives override ( #61641 )
...
Follow-up to https://github.com/vercel/next.js/pull/61637 seeing if the
overrides change is impacting the publish error.
Closes NEXT-2352
2024-02-04 14:06:54 -08:00
vercel-release-bot
db24fc0c3f
v14.1.1-canary.31
2024-02-04 20:10:43 +00:00
vercel-release-bot
bedfeac4e3
v14.1.1-canary.30
2024-02-03 23:21:46 +00:00
vercel-release-bot
aa66300f75
v14.1.1-canary.29
2024-02-02 23:21:11 +00:00
OJ Kwon
b95e45a511
build(cargo): bump up turbopack ( #61590 )
...
* https://github.com/vercel/turbo/pull/7213 <!-- OJ Kwon -
feat(turbopack): extend ecmatransform moduleeffect -->
* https://github.com/vercel/turbo/pull/7219 <!-- Leah - fix(turbopack):
encode source map urls -->
* https://github.com/vercel/turbo/pull/7220 <!-- Leah -
style(turbopack): make idents more readable -->
Closes PACK-2369
2024-02-02 12:22:42 -08:00
Donny/강동윤
a77f8a9165
Update turbopack ( #61553 )
...
# Turbopack
* https://github.com/vercel/turbo/pull/7207 <!-- Donny/강동윤 -
feat(turbopack): Enable error recovery of lightningcss -->
* https://github.com/vercel/turbo/pull/7096 <!-- Tobias Koppers -
migrate type references to primary references -->
* https://github.com/vercel/turbo/pull/7225 <!-- Donny/강동윤 -
fix(turbopack): Fix css var issue and font issue when using
`lightningcss` -->
### What?
Update turbopack
### Why?
To test https://github.com/vercel/turbo/pull/7225 against internal apps.
### How?
Closes PACK-2364
2024-02-02 08:27:00 +00:00
Balázs Orbán
d43a387d27
chore: update ESLint and plugins to latest ( #61544 )
...
Bumping ESLint to the newest version.
Related: #61525
Closes NEXT-2336
2024-02-01 20:06:02 -05:00
vercel-release-bot
5cd7790091
v14.1.1-canary.28
2024-02-01 23:21:30 +00:00
Steven
5ee6a07d74
fix: bump @vercel/nft@0.26.3 ( #61538 )
...
- Release notes https://github.com/vercel/nft/releases/tag/0.26.3
- Fixes https://github.com/vercel/next.js/issues/59346
- Related to https://github.com/lovell/sharp/issues/3967
Closes NEXT-2334
2024-02-01 16:46:38 -05:00
Kiko Beats
461aa5108e
build: upgrade edge-runtime ( #61030 )
...
It exposes `performance` constructor
Closes #60433
Closes NEXT-2195
2024-02-01 13:10:12 +01:00
Steven
9d949fd428
chore(deps): bump swr to 2.2.4 ( #61480 )
...
- Closes https://github.com/vercel/next.js/pull/61478
Closes NEXT-2319
2024-02-01 00:29:04 +00:00
vercel-release-bot
a35f689c5b
v14.1.1-canary.27
2024-01-31 23:21:57 +00:00
vercel-release-bot
dbd9598f56
v14.1.1-canary.26
2024-01-31 18:11:07 +00:00
Donny/강동윤
fafcb5fbfe
Update turbopack ( #61433 )
...
# Turbopack
* https://github.com/vercel/turbo/pull/7167 <!-- Leah - fix: catch
import map lookup error properly in `ResolvingIssue` -->
* https://github.com/vercel/turbo/pull/7182 <!-- Donny/강동윤 - feat:
Re-enable `preset-env` mode of `styled-jsx` in turbopack -->
* https://github.com/vercel/turbo/pull/7161 <!-- Tobias Koppers - add
support for globs in sideEffects field in package.json -->
* https://github.com/vercel/turbo/pull/7184 <!-- Donny/강동윤 - chore:
Update `swc_core` to `v0.89.6` -->
### What?
Update turbopack
### Why?
To test https://github.com/vercel/turbo/pull/7182 against internal
webapps.
### How?
- Closes #57718
Closes PACK-2334
2024-01-31 19:33:37 +09:00
vercel-release-bot
6df41fde43
v14.1.1-canary.25
2024-01-31 00:29:05 +00:00
vercel-release-bot
7c4d724e57
v14.1.1-canary.24
2024-01-30 23:22:57 +00:00
vercel-release-bot
1eecfc7d74
v14.1.1-canary.23
2024-01-30 19:02:50 +00:00
vercel-release-bot
62bba1982e
v14.1.1-canary.22
2024-01-30 14:37:47 +00:00
