archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/Cargo.toml

133 lines
4 KiB
TOML
Raw Normal View History

Add/wasm build (#31470)
2021-11-17 20:01:02 +01:00
[workspace]
Add initial next swc package with first transform (#27355) * Set up next-swc package with no custom transforms * Add hook_optimizer transform * Fix lint * Build next-swc on CI * Add toolchain in rust action * Build binaries in manual workflow * Commit from GitHub Actions (Build next-swc native binaries) * Update dependencies * Update swc and use stable rust * Build next-swc binaries * Test compiled code * Dedupe @node-rs/helper * Add workflow to check next-swc binaries * Fix check native * PR feedback * PR feedback * Pr feedback * Build next-swc binaries * Combine native workflows * Add docs for contributors on less common platforms * PR feedback * Compare JsWord instead of converting to string * Fix workflow formatting * Add docs for building binaries for CI * Build next-swc binaries * Fix workflow if syntax * Add license info to copied code Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2021-07-27 17:07:28 +02:00
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
members = [
Add trace-to-jaeger to workspace (#49692) ## What? I wasn't able to `cargo run` in trace-to-jaeger because it wasn't in the workspace. <!-- 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 or adding/fixing 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 # -->
2023-05-12 12:28:41 +02:00
"scripts/send-trace-to-jaeger",
build(cargo): move workspaces manifest to top level (#48198) <!-- 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 or adding/fixing 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 changes to the `root` of the cargo workspace to the root of repo itself, allows next-swc and other rust codebase can use repo root as workspace root. ### Why? Currently cargo manifest for the next-swc is not placed under the root of the repo, which makes invocation to the tool requires to change cwd / or set cwd. Similarly needs to open editor to the root of the cargo manifest separately to able to utilize language server kicks in. Moving manifest to the root consolidates those, so can invoke either cli / or editor to the same root of the repo.
2023-04-19 18:38:36 +02:00
"packages/next-swc/crates/core",
"packages/next-swc/crates/napi",
"packages/next-swc/crates/wasm",
"packages/next-swc/crates/next-build",
"packages/next-swc/crates/next-core",
"packages/next-swc/crates/next-dev",
"packages/next-swc/crates/next-dev-tests",
"packages/next-swc/crates/next-transform-font",
"packages/next-swc/crates/next-transform-dynamic",
"packages/next-swc/crates/next-transform-strip-page-exports",
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
]
Add/amp attribute patcher (#27700) * Add amp attribute transform * Add amp attribute unit tests * Fix ci if statements * Checkout code in rust tests * Add rust fixtures to eslintignore * Add cargo config * Configure toolchain for cross compilation
2021-08-03 18:54:57 +02:00
feat(next-swc): Update swc crates (#35395) * Update crates * fixup * fix type * Update test refs * Update css crates * Update test refs * Update test refs * Update test refs * SourceMap * Fix? * Update crates * Fix * Update test refs * Update test refs * Update error reporter * Update snapshots * Update snapshots * Bug? * Fix * Fix lint * Update swc again * fixup * Update test refs * Fix Co-authored-by: Maia Teegarden <dev@padmaia.rocks>
2022-03-31 00:13:40 +02:00
[profile.dev.package.swc_css_prefixer]
opt-level = 2
chore: Update swc_core to `v0.28.10` (#41016) This PR updates swc crates to https://github.com/swc-project/swc/commit/447e2449d9839f8d6ccff748e6a34d8123e82169
2022-09-29 16:09:20 +02:00
# This is a workaround for wasm timeout issue
[profile.dev.package."*"]
debug-assertions = false
Add/amp attribute patcher (#27700) * Add amp attribute transform * Add amp attribute unit tests * Fix ci if statements * Checkout code in rust tests * Add rust fixtures to eslintignore * Add cargo config * Configure toolchain for cross compilation
2021-08-03 18:54:57 +02:00
[profile.release]
build(next/swc): consolidate swc_core dependency version (#41043) <!-- 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 that you're making: --> This PR utilizes cargo's new feature from latest release (1.64.0), inheriting dependency from a workspace. In short, top-level workspace cargo manifest can specify a version of dependency to use, then actual packages uses it without re-declaring version per each via workspace = true. This will help to dedupe different versions of packages, also potentially avoid conflicts if forgot to bump up specific versions. In this pr only touches swc_core, which is a base dependency we use in several place. One another benefit for this is bump up PR can be lot more simplified, only need to update single Cargo.toml when we bump up. Note rust-toolchain has updated to use nightly version after 1.64.0 to enable this. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
2022-09-30 21:59:32 +02:00
lto = true
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
[workspace.dependencies]
# Workspace crates
Next Build Turbo POC (2) (#51546) Another attempt at getting https://github.com/vercel/next.js/pull/49942 in. This time, the mold install step is gated to Linux.
2023-06-22 10:03:44 +02:00
next-build = { path = "packages/next-swc/crates/next-build", default-features = false }
build(cargo): move workspaces manifest to top level (#48198) <!-- 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 or adding/fixing 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 changes to the `root` of the cargo workspace to the root of repo itself, allows next-swc and other rust codebase can use repo root as workspace root. ### Why? Currently cargo manifest for the next-swc is not placed under the root of the repo, which makes invocation to the tool requires to change cwd / or set cwd. Similarly needs to open editor to the root of the cargo manifest separately to able to utilize language server kicks in. Moving manifest to the root consolidates those, so can invoke either cli / or editor to the same root of the repo.
2023-04-19 18:38:36 +02:00
next-core = { path = "packages/next-swc/crates/next-core", default-features = false }
next-dev = { path = "packages/next-swc/crates/next-dev", default-features = false, features = [
Turobpack: Implement Streaming App/API rendering (#47476) Paired with https://github.com/vercel/turbo/pull/4329, this implements streaming responses for App and API renders. This is accomplished by sending an initial `headers` message (carrying the status code and headers list), N `body-chunk` messages of bytes, and a final `body-end` message to signal completion. Once sent to Turbopack, these chunk messages will be streamed out of the node rendering process directly into the HTTP server's response. Closes WEB-27 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-03-31 20:58:04 +02:00
"serializable",
] }
build(cargo): move workspaces manifest to top level (#48198) <!-- 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 or adding/fixing 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 changes to the `root` of the cargo workspace to the root of repo itself, allows next-swc and other rust codebase can use repo root as workspace root. ### Why? Currently cargo manifest for the next-swc is not placed under the root of the repo, which makes invocation to the tool requires to change cwd / or set cwd. Similarly needs to open editor to the root of the cargo manifest separately to able to utilize language server kicks in. Moving manifest to the root consolidates those, so can invoke either cli / or editor to the same root of the repo.
2023-04-19 18:38:36 +02:00
next-dev-tests = { path = "packages/next-swc/crates/next-dev-tests" }
next-transform-font = { path = "packages/next-swc/crates/next-transform-font" }
next-transform-dynamic = { path = "packages/next-swc/crates/next-transform-dynamic" }
next-transform-strip-page-exports = { path = "packages/next-swc/crates/next-transform-strip-page-exports" }
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
# SWC crates
# Keep consistent with preset_env_base through swc_core
Update swc_core to `v0.79.13` (#52371) ### What? Update SWC crates to `v0.79.13`. ### Why? - Explicit resource management proposal is now fully implemented, although it's behind a parser flag because it's stage 3 - Some bugs of `swcMinify` are fixed. ### How? Closes WEB-1272 ## Turbopack updates * https://github.com/vercel/turbo/pull/5475 Co-authored-by: Alex Kirszenberg <1621758+alexkirsz@users.noreply.github.com>
2023-07-07 21:37:05 +02:00
swc_core = { version = "0.79.13" }
testing = { version = "0.33.20" }
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
# Turbo crates
Turbopack: Source trait (#52511) ### What? refactoring see https://github.com/vercel/turbo/pull/5483 ### Turbopack Changes * https://github.com/vercel/turbo/pull/5483 <!-- Tobias Koppers - Source trait -->
2023-07-11 12:34:32 +02:00
turbopack-binding = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230711.2" }
build(next-swc): introduce turbo-binding (#47512) <!-- 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 or adding/fixing 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? Part of WEB-736. This PR refactors imports to turbopack to turbo-binding, as same as we used to do with next-binding. Current next-binding in this repo doesn't make sense anymore and removed. There are no functional changes. This'll reducwe surface for the imports and also will make easier to run integration test over latest turbopack. Note swc dependency is not reflected in this PR yet - following PR will update those imports.
2023-03-30 05:25:11 +02:00
# [TODO]: need to refactor embed_directory! macro usages, as well as resolving turbo_tasks::function, macros..
Turbopack: Source trait (#52511) ### What? refactoring see https://github.com/vercel/turbo/pull/5483 ### Turbopack Changes * https://github.com/vercel/turbo/pull/5483 <!-- Tobias Koppers - Source trait -->
2023-07-11 12:34:32 +02:00
turbo-tasks = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230711.2" }
build(next-swc): introduce turbo-binding (#47512) <!-- 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 or adding/fixing 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? Part of WEB-736. This PR refactors imports to turbopack to turbo-binding, as same as we used to do with next-binding. Current next-binding in this repo doesn't make sense anymore and removed. There are no functional changes. This'll reducwe surface for the imports and also will make easier to run integration test over latest turbopack. Note swc dependency is not reflected in this PR yet - following PR will update those imports.
2023-03-30 05:25:11 +02:00
# [TODO]: need to refactor embed_directory! macro usage in next-core
Turbopack: Source trait (#52511) ### What? refactoring see https://github.com/vercel/turbo/pull/5483 ### Turbopack Changes * https://github.com/vercel/turbo/pull/5483 <!-- Tobias Koppers - Source trait -->
2023-07-11 12:34:32 +02:00
turbo-tasks-fs = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230711.2" }
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
# General Deps
# Be careful when selecting tls backend, including change default tls backend.
# If you changed, must verify with ALL build targets with next-swc to ensure
# it works. next-swc have various platforms, some doesn't support native (using openssl-sys)
# and some aren't buildable with rustls.
reqwest = { version = "0.11.14", default-features = false }
add turbopack integration tests to CI (#50904) ### 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>
2023-06-12 16:47:43 +02:00
chromiumoxide = { version = "0.5.0", features = [
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
"tokio-runtime",
], default-features = false }
# For matching on errors from chromiumoxide. Keep in
# sync with chromiumoxide's tungstenite requirement.
add turbopack integration tests to CI (#50904) ### 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>
2023-06-12 16:47:43 +02:00
tungstenite = "0.18.0"
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
Implement automatic font fallback support for `next/font/local` (#47463) Fixes WEB-787. This implements automatic font fallbacks for `next/font/local`. It uses the `allsorts` library to query font metrics across woff and ttf fonts. Test Plan: Now passes 24 Next.js integration tests, up from 14.
2023-03-28 03:22:48 +02:00
# flate2_zlib requires zlib, use flate2_rust
Turobpack: Implement Streaming App/API rendering (#47476) Paired with https://github.com/vercel/turbo/pull/4329, this implements streaming responses for App and API renders. This is accomplished by sending an initial `headers` message (carrying the status code and headers list), N `body-chunk` messages of bytes, and a final `body-end` message to signal completion. Once sent to Turbopack, these chunk messages will be streamed out of the node rendering process directly into the HTTP server's response. Closes WEB-27 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-03-31 20:58:04 +02:00
allsorts = { version = "0.14.0", default_features = false, features = [
"outline",
"flate2_rust",
] }
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
anyhow = "1.0.69"
assert_cmd = "2.0.8"
async-compression = { version = "0.3.13", default-features = false, features = [
"gzip",
"tokio",
] }
async-trait = "0.1.64"
atty = "0.2.14"
chrono = "0.4.23"
clap = "4.1.6"
clap_complete = "4.1.2"
concurrent-queue = "2.1.0"
console = "0.15.5"
console-subscriber = "0.1.8"
criterion = "0.4.0"
add tracing for turbopack (#49920) ### What? adds `NEXT_TURBOPACK_TRACING` env var to enable tracing. Writes into `.next/trace.log` There are 4 presets: * `NEXT_TURBOPACK_TRACING=overview` gives a overview of requests and modules processed. * `NEXT_TURBOPACK_TRACING=next` above plus details for next.js * `NEXT_TURBOPACK_TRACING=turbopack` above plus details for turbopack * `NEXT_TURBOPACK_TRACING=turbo-tasks` above plus details for turbo-tasks Published release builds will only allow `overview` to work, since all detailed instrumentation is statically disabled. see https://github.com/vercel/turbo/pull/4966 for more details ### Why? get more insight into build times ### Turbopack changes * https://github.com/vercel/turbo/pull/4995 * https://github.com/vercel/turbo/pull/5049 * https://github.com/vercel/turbo/pull/5053 * https://github.com/vercel/turbo/pull/4966
2023-05-23 07:25:56 +02:00
crossbeam-channel = "0.5.8"
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
dashmap = "5.4.0"
dialoguer = "0.10.3"
dunce = "1.0.3"
futures = "0.3.26"
futures-retry = "0.6.0"
fix build issue and future incompatibility (#47176) It was complaining about having 2 versions of sentry for some reason
2023-03-16 20:29:24 +01:00
httpmock = { version = "0.6.7", default-features = false }
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
indexmap = "1.9.2"
indicatif = "0.17.3"
indoc = "2.0.0"
itertools = "0.10.5"
lazy_static = "1.4.0"
log = "0.4.17"
mime = "0.3.16"
nohash-hasher = "0.2.0"
once_cell = "1.17.1"
owo-colors = "3.5.0"
parking_lot = "0.12.1"
pathdiff = "0.2.1"
pin-project-lite = "0.2.9"
add tracing for turbopack (#49920) ### What? adds `NEXT_TURBOPACK_TRACING` env var to enable tracing. Writes into `.next/trace.log` There are 4 presets: * `NEXT_TURBOPACK_TRACING=overview` gives a overview of requests and modules processed. * `NEXT_TURBOPACK_TRACING=next` above plus details for next.js * `NEXT_TURBOPACK_TRACING=turbopack` above plus details for turbopack * `NEXT_TURBOPACK_TRACING=turbo-tasks` above plus details for turbo-tasks Published release builds will only allow `overview` to work, since all detailed instrumentation is statically disabled. see https://github.com/vercel/turbo/pull/4966 for more details ### Why? get more insight into build times ### Turbopack changes * https://github.com/vercel/turbo/pull/4995 * https://github.com/vercel/turbo/pull/5049 * https://github.com/vercel/turbo/pull/5053 * https://github.com/vercel/turbo/pull/4966
2023-05-23 07:25:56 +02:00
postcard = "1.0.4"
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
predicates = "2.1.5"
pretty_assertions = "1.3.0"
proc-macro2 = "1.0.51"
qstring = "0.7.2"
quote = "1.0.23"
rand = "0.8.5"
regex = "1.7.0"
rstest = "0.16.0"
rustc-hash = "1.1.0"
semver = "1.0.16"
serde = { version = "1.0.152", features = ["derive"] }
serde_json = "1.0.93"
serde_qs = "0.11.0"
serde_yaml = "0.9.17"
syn = "1.0.107"
tempfile = "3.3.0"
thiserror = "1.0.38"
tiny-gradient = "0.1.0"
tokio = "1.25.0"
tokio-util = { version = "0.7.7", features = ["io"] }
tracing = "0.1.37"
add tracing for turbopack (#49920) ### What? adds `NEXT_TURBOPACK_TRACING` env var to enable tracing. Writes into `.next/trace.log` There are 4 presets: * `NEXT_TURBOPACK_TRACING=overview` gives a overview of requests and modules processed. * `NEXT_TURBOPACK_TRACING=next` above plus details for next.js * `NEXT_TURBOPACK_TRACING=turbopack` above plus details for turbopack * `NEXT_TURBOPACK_TRACING=turbo-tasks` above plus details for turbo-tasks Published release builds will only allow `overview` to work, since all detailed instrumentation is statically disabled. see https://github.com/vercel/turbo/pull/4966 for more details ### Why? get more insight into build times ### Turbopack changes * https://github.com/vercel/turbo/pull/4995 * https://github.com/vercel/turbo/pull/5049 * https://github.com/vercel/turbo/pull/5053 * https://github.com/vercel/turbo/pull/4966
2023-05-23 07:25:56 +02:00
tracing-subscriber = "0.3.16"
Integrate next-* crates from Turbopack (#47019) Update workspace cargo deps Update cargo deps to point to local workspace Ignore too-many-arguments warnings Fix clippy errors Update pnpm workspaces exclude integration tests from unit tests CI rust-analyzer settings add rust flags and env vars
2023-03-10 21:59:54 +01:00
url = "2.2.2"
urlencoding = "2.1.2"
webbrowser = "0.8.7"
feat(next-swc): add compile-time heap profiler flag (#47729) ### What? This PR adds an internal compile time flags for the `next-swc`, which exposes two runtime apis into next.js to initialize heap-profiling enabled memory allocator and teardown those once next.js exits. While there are newly added 2 js interfaces (`initHeapProfiler`, `teardownHeapProfiler`) underlying napi binary itself have compile time flags to actually enable those feature: any user who runs npm-published next.js cannot enable this features with any kind of runtime configuration. Only manually built next-swc binary with specific flag can enable this. Since this is primarily for the CI testing workflow only, those flag / configs are not visibily exposed as well. ### Why? It is for some experiments on the CI to see if it can observe some of memory pressure issues (WEB-593, WEB-804) while it is not easily reproducible on the local machines.
2023-03-31 10:37:17 +02:00
dhat = { version = "0.3.2" }
Reference in a new issue Copy permalink