The `naka-bundler` package (current version 0.0.7) provides a specialized command-line interface (CLI) for bundling and transpiling JavaScript and TypeScript files. It acts as a lightweight wrapper around Bun, leveraging Bun's performance characteristics to achieve fast compilation times. Developed as an integral part of the `naka` project, it specifically targets browser automation workflows, optimizing file transformations for that context. A key design principle is its performance, achieved by compiling itself into an executable binary using Bun. This allows for rapid execution without reliance on a globally installed `bun` runtime for the end-user. The bundler offers a "batteries-included" experience with no configuration options, making it ideal for straightforward bundling tasks where customization is not required. For advanced or custom configurations, users are advised to interact with Bun directly rather than through `naka-bundler`. As an early-stage project (v0.0.7), its release cadence is likely tied to the development of the broader `naka` ecosystem.
npm install naka-bundlerVerified import paths — ran on the pinned version, not inferred.
Illustrates bundling 'src/index.ts' and outputting the transpiled result to the 'dist/out' directory using the `naka-bundler` CLI.
Consult the latest GitHub README for current CLI usage. Use tools like `npm install naka-bundler@0.0.7` to pin the version in your projects.
For customizable bundling needs, utilize `bun` directly, which offers extensive configuration, or explore other bundlers like Webpack, Rollup, or Esbuild.
Interact with `naka-bundler` exclusively through your shell or scripts via `npx naka-bundler ...`.
This package is a CLI. Do not import it; instead, run it directly from your terminal using `npx naka-bundler entry.ts output_dir`.
Ensure `npm` is installed and updated. Use `npx naka-bundler ...` to execute, which handles on-demand installation, or install globally with `npm install -g naka-bundler` for frequent direct invocation.
Verify the absolute or relative path to your entry TypeScript/JavaScript file. Ensure the file specified actually exists at the provided location.
No dependency data recorded yet.