move core node-file-trace logic into turbopack

vercel · Oct 11, 2024 · 9eb8143 · 9eb8143
1 parent a2bfe3f
commit 9eb8143
Show file tree

Hide file tree

Showing 8 changed files with 435 additions and 337 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/turbopack/crates/node-file-trace/Cargo.toml b/turbopack/crates/node-file-trace/Cargo.toml
@@ -45,3 +45,6 @@ turbopack-resolve = { workspace = true }
 
 [build-dependencies]
 turbo-tasks-build = { workspace = true }
+
+[dev-dependencies]
+insta = "1.40.0"
diff --git a/turbopack/crates/node-file-trace/readme.md b/turbopack/crates/node-file-trace/readme.md
@@ -0,0 +1,18 @@
+# node-file-trace
+
+Node file trace (nft) is a binary / library that can be used to precisely determine
+which files (including those in `node_modules`) are needed for a given application at
+run time.
+
+## Usage
+
+There are a few commands available (accessed via the `Args` struct if consuming as a
+library). You can see these by running the binary. The binary should be self-documenting.
+
+```bash
+cargo run
+```
+
+## Externals
+
+Tracing externals is not currently supported, though support will be added soon.