Turbopack JS entrypoint and native build entrypoint using napi
In order to integrate Turbopack more cleanly into our benchmarking suite, we need to have a standalone Turbopack binary that can isolate the bundler behavior without including Next crates. This commit is basically boilerplate necessary to bridge JS and Rust, without actually hooking into build functionality. It looks for and parses a config file (necessary for benchmark suites later) but does nothing with it. The next PR in the stack will actually run a basic build from the selected entrypoint.
Showing
packages/turbopack/README.md
0 → 100644
Please
register
or
sign in
to comment