archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/packages/next-swc/crates/next-dev/Cargo.toml

53 lines
1.4 KiB
TOML
Raw Normal View History

add initial dev-server and next-dev cli
2022-06-14 10:48:25 +02:00
[package]
name = "next-dev"
version = "0.1.0"
edition = "2021"
[[bin]]
name = "next-dev"
path = "src/main.rs"
bench = false
Extract server creation into own function and module (vercel/turbo#191) * Extract server creation into fn * Use builder pattern and anyhow context
2022-08-03 01:28:11 +02:00
[lib]
fix css layer import (vercel/turbo#195) kdy1 fixes this upstream
2022-08-03 05:37:56 +02:00
bench = false
Extract server creation into own function and module (vercel/turbo#191) * Extract server creation into fn * Use builder pattern and anyhow context
2022-08-03 01:28:11 +02:00
add initial dev-server and next-dev cli
2022-06-14 10:48:25 +02:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
improve visualization make TransientValue functional make console-subscriber an optional feature avoid cloning when calling a function capture timings of task executions fix LazyAsset expose graph from dev server
2022-07-07 14:27:15 +02:00
[features]
Node Module Trace webpack plugin (vercel/turbo#140) * Initialize Node.js/TypeScript workspace * node-module-trace Webpack plugin * Add new fmt checks to pipeline * Popup unwind error * Implement --exact flag * Yarn 3.2.2 * Reformat toml files * Fix socket io test, 100ms timeout is too long * remove unnecessary CI cache config * regenerate lockfile from old lockfile, align the dependencies version * Run nmt tests in system tmp dir * Apply code review suggestions * allow to wait for task completion and propagate errors and panics * revert method addition * spawn_root_task should be sync Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2022-07-22 12:36:08 +02:00
tokio_console = [
"dep:console-subscriber",
"tokio/tracing",
"turbo-tasks/tokio_tracing",
]
improve visualization make TransientValue functional make console-subscriber an optional feature avoid cloning when calling a function capture timings of task executions fix LazyAsset expose graph from dev server
2022-07-07 14:27:15 +02:00
add initial dev-server and next-dev cli
2022-06-14 10:48:25 +02:00
[dependencies]
Node Module Trace webpack plugin (vercel/turbo#140) * Initialize Node.js/TypeScript workspace * node-module-trace Webpack plugin * Add new fmt checks to pipeline * Popup unwind error * Implement --exact flag * Yarn 3.2.2 * Reformat toml files * Fix socket io test, 100ms timeout is too long * remove unnecessary CI cache config * regenerate lockfile from old lockfile, align the dependencies version * Run nmt tests in system tmp dir * Apply code review suggestions * allow to wait for task completion and propagate errors and panics * revert method addition * spawn_root_task should be sync Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2022-07-22 12:36:08 +02:00
anyhow = "1.0.47"
don't like these quoted names lol
2022-06-29 17:34:15 +02:00
clap = { version = "3.1.3", features = ["derive"] }
Node Module Trace webpack plugin (vercel/turbo#140) * Initialize Node.js/TypeScript workspace * node-module-trace Webpack plugin * Add new fmt checks to pipeline * Popup unwind error * Implement --exact flag * Yarn 3.2.2 * Reformat toml files * Fix socket io test, 100ms timeout is too long * remove unnecessary CI cache config * regenerate lockfile from old lockfile, align the dependencies version * Run nmt tests in system tmp dir * Apply code review suggestions * allow to wait for task completion and propagate errors and panics * revert method addition * spawn_root_task should be sync Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2022-07-22 12:36:08 +02:00
console-subscriber = { version = "0.1.6", optional = true }
next-dev test runner (vercel/turbo#172) This is a very early version of the next-dev test runner. I'm opening this early to get thoughts from folks re: the direction of the design and implementation. Fixes vercel/turbo#204 Currently it: * Discovers integration test fixtures from the filesystem. Right now these are expected to be single files that get bundled and will eventually include assertions. This is powered by the test-generator crate, which allows us not to have to manually enumerate each case. We could consider using this for the node-file-trace tests as well. * Starts the dev server on a free port and opens a headless browser to its root. The browser control is implemented with the https://crates.io/crates/chromiumoxide crate, which expects Chrome or Chromium to already be available. Eventually it will: * [x] Implement a minimal test environment loaded in the browser so that assertions can be run there from bundled code. * [x] Report back the results of these assertions to rust, where we can pass/fail cargo tests with those results. In the future it could: * Possibly include snapshot-style tests to assert on transformed results. This could be in the form of fixture directories instead of files cc @jridgewell * Support expressing special configuration of turbopack in a fixture, possibly as another file in the fixture directory. * [x] ~Possibly support distributing tests to a pool of open browsers instead of opening and closing for each test.~ Test Plan: See next PRs
2022-08-09 18:20:30 +02:00
futures = "0.3.21"
Node Module Trace webpack plugin (vercel/turbo#140) * Initialize Node.js/TypeScript workspace * node-module-trace Webpack plugin * Add new fmt checks to pipeline * Popup unwind error * Implement --exact flag * Yarn 3.2.2 * Reformat toml files * Fix socket io test, 100ms timeout is too long * remove unnecessary CI cache config * regenerate lockfile from old lockfile, align the dependencies version * Run nmt tests in system tmp dir * Apply code review suggestions * allow to wait for task completion and propagate errors and panics * revert method addition * spawn_root_task should be sync Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2022-07-22 12:36:08 +02:00
json = "0.12.4"
introduce ContentSource as source for the dev server (vercel/turbo#185) and potentially a next build in future
2022-08-01 09:02:53 +02:00
mime = "0.3.16"
add basic next pages support (vercel/turbo#223) Server Rendering: * This adds an additional ContentSource to next-dev which takes care of handling the `pages` directory. * The content source creates a ServerRenderedAsset from each file in the `src/pages` or `pages` directory and a AssetGraphContentSource for that. * The ServerRenderedAsset will reference an underlying asset for the node.js context which will be passed to the node executable for rendering. It uses a WrapperAsset to add additional communication logic. Client Transition: * When annotating `import`s with `transition: "next-client"` the NextClientTransition is used * This transition changes the environment to browser * It wraps the referenced asset with a next-hyrdation wrapper asset * It leaves a little module in the previous context which exports a list of URLs for chunks needed. * The NextClientTransition takes a client_chunking_context as argument which specifies how the client code is chunked.
2022-08-15 19:26:37 +02:00
next-core = { path = "../next-core" }
Node Module Trace webpack plugin (vercel/turbo#140) * Initialize Node.js/TypeScript workspace * node-module-trace Webpack plugin * Add new fmt checks to pipeline * Popup unwind error * Implement --exact flag * Yarn 3.2.2 * Reformat toml files * Fix socket io test, 100ms timeout is too long * remove unnecessary CI cache config * regenerate lockfile from old lockfile, align the dependencies version * Run nmt tests in system tmp dir * Apply code review suggestions * allow to wait for task completion and propagate errors and panics * revert method addition * spawn_root_task should be sync Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2022-07-22 12:36:08 +02:00
serde = "1.0.136"
tokio = { version = "1.11.0", features = ["full"] }
don't like these quoted names lol
2022-06-29 17:34:15 +02:00
turbo-tasks = { path = "../turbo-tasks" }
turbo-tasks-fs = { path = "../turbo-tasks-fs" }
Node Module Trace webpack plugin (vercel/turbo#140) * Initialize Node.js/TypeScript workspace * node-module-trace Webpack plugin * Add new fmt checks to pipeline * Popup unwind error * Implement --exact flag * Yarn 3.2.2 * Reformat toml files * Fix socket io test, 100ms timeout is too long * remove unnecessary CI cache config * regenerate lockfile from old lockfile, align the dependencies version * Run nmt tests in system tmp dir * Apply code review suggestions * allow to wait for task completion and propagate errors and panics * revert method addition * spawn_root_task should be sync Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2022-07-22 12:36:08 +02:00
turbo-tasks-memory = { path = "../turbo-tasks-memory" }
don't like these quoted names lol
2022-06-29 17:34:15 +02:00
turbopack = { path = "../turbopack" }
add issue reporting to next dev (vercel/turbo#208)
2022-08-08 09:39:52 +02:00
turbopack-cli-utils = { path = "../turbopack-cli-utils" }
don't like these quoted names lol
2022-06-29 17:34:15 +02:00
turbopack-core = { path = "../turbopack-core" }
turbopack-dev-server = { path = "../turbopack-dev-server" }
Move browser opening to next-dev cli (vercel/turbo#169) Cherry-picking this from my work on the next-dev test runner. This moves browser opening from the turbopack-dev-server crate into the next-dev crate, which has the cli entrypoint that runs the dev server. It looks like the dev server package is meant to be used as a library (it's only a library crate), and having this external side effect feels unexpected and makes it difficult to use this crate in situations like a test runner for next-dev, where we should test with a headless web browser. Alternatively, opening the browser could be an option passed when creating the dev server, but this feels a bit cleaner to me. Test Plan: `cargo run -p next-dev` and verify the browser still opens and successfully connects to the dev server.
2022-07-27 21:09:11 +02:00
webbrowser = "0.7.1"
add initial dev-server and next-dev cli
2022-06-14 10:48:25 +02:00
next-dev test runner (vercel/turbo#172) This is a very early version of the next-dev test runner. I'm opening this early to get thoughts from folks re: the direction of the design and implementation. Fixes vercel/turbo#204 Currently it: * Discovers integration test fixtures from the filesystem. Right now these are expected to be single files that get bundled and will eventually include assertions. This is powered by the test-generator crate, which allows us not to have to manually enumerate each case. We could consider using this for the node-file-trace tests as well. * Starts the dev server on a free port and opens a headless browser to its root. The browser control is implemented with the https://crates.io/crates/chromiumoxide crate, which expects Chrome or Chromium to already be available. Eventually it will: * [x] Implement a minimal test environment loaded in the browser so that assertions can be run there from bundled code. * [x] Report back the results of these assertions to rust, where we can pass/fail cargo tests with those results. In the future it could: * Possibly include snapshot-style tests to assert on transformed results. This could be in the form of fixture directories instead of files cc @jridgewell * Support expressing special configuration of turbopack in a fixture, possibly as another file in the fixture directory. * [x] ~Possibly support distributing tests to a pool of open browsers instead of opening and closing for each test.~ Test Plan: See next PRs
2022-08-09 18:20:30 +02:00
[dev-dependencies]
next-dev test runner: Implement manual debug mode (vercel/turbo#211) This implements a manual debug mode for next-dev tests, enabled by setting the environment variable TURBOPACK_DEBUG_BROWSER to any value. It launches the test browser in non-headless mode and holds it open ~~indefinitely~~ until the user closes it, so it can be inspected. Test Plan: `TURBOPACK_DEBUG_BROWSER=1 cargo test -p next-dev -- test_crates_next_dev_tests_integration_chunks_circular_correctness --nocapture` and verify the browser is opened non-headless and is held open
2022-08-10 12:14:01 +02:00
tungstenite = "0.17.3" # For matching on errors from chromiumoxide. Keep in
# sync with chromiumoxide's tungstenite requirement.
next-dev test runner (vercel/turbo#172) This is a very early version of the next-dev test runner. I'm opening this early to get thoughts from folks re: the direction of the design and implementation. Fixes vercel/turbo#204 Currently it: * Discovers integration test fixtures from the filesystem. Right now these are expected to be single files that get bundled and will eventually include assertions. This is powered by the test-generator crate, which allows us not to have to manually enumerate each case. We could consider using this for the node-file-trace tests as well. * Starts the dev server on a free port and opens a headless browser to its root. The browser control is implemented with the https://crates.io/crates/chromiumoxide crate, which expects Chrome or Chromium to already be available. Eventually it will: * [x] Implement a minimal test environment loaded in the browser so that assertions can be run there from bundled code. * [x] Report back the results of these assertions to rust, where we can pass/fail cargo tests with those results. In the future it could: * Possibly include snapshot-style tests to assert on transformed results. This could be in the form of fixture directories instead of files cc @jridgewell * Support expressing special configuration of turbopack in a fixture, possibly as another file in the fixture directory. * [x] ~Possibly support distributing tests to a pool of open browsers instead of opening and closing for each test.~ Test Plan: See next PRs
2022-08-09 18:20:30 +02:00
chromiumoxide = { version = "0.3.5", features = [
"tokio-runtime",
], default-features = false }
lazy_static = "1.4.0"
test-generator = "0.3.0"
add initial dev-server and next-dev cli
2022-06-14 10:48:25 +02:00
[build-dependencies]
don't like these quoted names lol
2022-06-29 17:34:15 +02:00
turbo-tasks-build = { path = "../turbo-tasks-build" }
Reference in a new issue Copy permalink