The `app-bundler` package is a JavaScript application bundler designed to support multiple module systems including CommonJS, MaskJS, IncludeJS, and AMD. Its core philosophy emphasizes a "no dependency" approach for the development process, aiming to be run only for deployments, and requires minimal configuration, often just a few lines in `package.json`. It focuses on single responsibility – combining modules into JS, CSS, and HTML bundles – and decouples pre- and post-processing through `atma-io` middlewares. This design allows for flexible integration with various preprocessors like TypeScript, Babel, Less, and Sass by utilizing `atma-io` plugins for file loading and transformation. The package is currently at version 0.2.18, and its GitHub repository shows no active development or commits for over six years as of 2026. Consequently, `app-bundler` is considered an abandoned project and is not recommended for new development or actively maintained systems due to potential security vulnerabilities, lack of compatibility with modern JavaScript ecosystems, and absence of community support. Developers should opt for contemporary, actively maintained bundling solutions.
npm install app-bundlerVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to invoke `app-bundler` using both its command-line interface via `npx` for a `package.json` script and a programmatic approach using its exported `bundle` function for a CommonJS application.
Migrate to actively maintained, modern bundlers like Webpack, Rollup, Vite, or Parcel. If migration is not immediately feasible for legacy projects, understand the security and compatibility risks.
For projects using ESM, configure a transpilation middleware (e.g., Babel via `atma-io` plugins) to convert ESM to CJS before `app-bundler` processes the files, or rewrite modules to use CommonJS `require()` syntax. Alternatively, use a modern bundler with native ESM support.
For sophisticated build requirements, be prepared to develop custom `atma-io` plugins or to orchestrate `app-bundler` within a larger, multi-tool build pipeline. Assess if a more feature-rich, opinionated bundler might be more suitable for your project's needs.
Ensure `atma-io` is listed in your project's `dependencies` or `devDependencies` and run `npm install` or `yarn install` to properly install it.
Install and configure an `atma-io` plugin that handles JavaScript transpilation (e.g., integrating Babel) to convert ES Modules to CommonJS. Alternatively, ensure all source files use CommonJS `require()` and `module.exports` syntax.
Verify and adjust the file system permissions for the output directory. On Unix-like systems, ensure the user has write access. If running as a build script, check the environment permissions. As a temporary measure, `sudo npx app-bundler` might work for CLI usage, but is not recommended for automated builds.