arenaless-bundler is a JavaScript/TypeScript bundler built upon Rollup, specifically designed for the ArenaLess ecosystem. Currently at version 1.1.7, its release cadence appears irregular, driven by project needs rather than a fixed schedule. A key differentiator is its support for a virtual file system, allowing builds to run in environments without direct file access, such as web browsers. It features Deno-like network imports, supporting `npm:`, `jsr:`, `http:`, and `https:` schemes (with `npm:` and `jsr:` resolving via `esm.sh`). The bundler also provides unique asset loading capabilities for local modules via special import suffixes like `?text`, `?base64`, `?binary`, and `?wasm`, alongside default JSON file importing. This focus on virtualized environments and flexible asset handling makes it suitable for specific web-based build pipelines or specialized module bundling needs.
npm install arenaless-bundlerVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to use `arenaless-bundler` to bundle a small virtual file system project, including local modules, special suffix imports, and network imports, outputting a CommonJS bundle.
Ensure that special suffixes are only applied to paths referencing files within the `Record<string, Uint8Array>` input to the `build` function. Network-imported modules must be consumed without these suffixes.
Be aware of the reliance on `esm.sh` for `npm:` and `jsr:` imports. For critical dependencies, consider vendoring them into your virtual file system or using direct `https:` imports if a specific CDN URL is preferred and stable.
Always convert string content to `Uint8Array` using `new TextEncoder().encode()` for text files, and ensure binary files are also provided as `Uint8Array`.
Verify that all imported modules are present as keys in the `files` object passed to `build`, and that the paths in `import` statements exactly match the keys in the virtual file system.
Ensure the `output_format` parameter in the `build` function call (e.g., set to `'cjs'` for CommonJS or `'esm'` for ES modules) matches the target environment's expectations. If bundling to CJS, ensure `package.json` doesn't force ESM; if to ESM, ensure `package.json` has `"type": "module"` or files end in `.mjs`.
These special suffixes are strictly for local modules within the virtual file system. Network imports must be consumed directly without any suffixes.
No dependency data recorded yet.