Lofi Bundler is a minimalist TypeScript utility designed for projects that prioritize simplicity and a zero-dependency build process, especially when targeting browser environments or when complex module loaders are unnecessary. It operates by walking through all specified TypeScript files within a project (explicitly excluding `node_modules` and other external folders) and concatenating their content into a single TypeScript bundle. This bundled file can then be fed into the standard TypeScript compiler (`tsc`) for final compilation, eliminating the need for more elaborate bundling solutions like Webpack, Rollup, or even Babel configurations. The package's current stable version is 1.0.1, suggesting a mature, feature-complete state with an infrequent release cadence focused on stability. Its primary differentiator lies in its 'lofi' philosophy: a bare-bones approach that avoids external dependencies and configuration overhead, making it ideal for small, self-contained utilities or libraries that need to run in both Node.js and the browser without introducing complex build chains or module resolution challenges inherent to different environments.
npm install lofi-bundlerVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to configure and run `lofi-bundler` via CLI in `package.json` scripts, including the subsequent `tsc` step for browser compatibility, and also shows programmatic API usage for direct integration.
Refactor your code to use named exports exclusively. For example, instead of `export default class MyClass {}`, use `export class MyClass {}`.Ensure your project truly has zero runtime dependencies, or manually manage external dependencies outside the lofi-bundler process (e.g., via `<script>` tags in HTML or a separate bundling step).
Always include `tsc` as a follow-up step in your build script after running `lofi-bundler`, configuring `tsc` with appropriate `--target` and `--module` options for your deployment environment.
Change all default exports to named exports. The bundler does not guarantee correct naming or resolution for default exports.
No dependency data recorded yet.