aurelia-bundler is a utility library specifically designed for bundling JavaScript, HTML, and CSS assets within applications built using the Aurelia 1 framework, leveraging SystemJS as the module loader. It provides programmatic APIs, commonly integrated into build automation tools like Gulp, to consolidate application modules and their dependencies into optimized bundles for production deployment. The package is considered abandoned, with its last release, version 0.7.0, dating back approximately eight years. It has been superseded by the built-in bundler provided by the Aurelia CLI for Aurelia 1 projects, and is not compatible with Aurelia 2, which has transitioned to modern bundlers such as Vite, Webpack, or Parcel. The package primarily addresses the bundling needs of legacy Aurelia 1 applications that explicitly relied on the SystemJS module ecosystem. Its release cadence was irregular towards the end of its active lifecycle, focusing on minor updates and bug fixes.
npm install aurelia-bundlerVerified import paths — ran on the pinned version, not inferred.
Demonstrates programmatic use of aurelia-bundler within a Gulp task to create application and vendor bundles for an Aurelia 1 SystemJS project.
For Aurelia 1 projects, migrate to the Aurelia CLI's built-in bundler. For new or migrating projects to Aurelia 2, use modern bundlers like Vite, Webpack, or Parcel with their respective Aurelia plugins.
Do not attempt to use `aurelia-bundler` with Aurelia 2. Aurelia 2 recommends Vite, Webpack, or Parcel.
When migrating an Aurelia 1 project from `aurelia-bundler` to another solution, pay close attention to module resolution and ensure that 'PLATFORM.moduleName()' (if used for Webpack) is either correctly translated or removed for Aurelia 2, which no longer requires it.
Ensure `tslib` is correctly configured and bundled. Verify that all dependencies are properly resolved and available at runtime. Review how the new bundler handles CommonJS/ESM interop and dependency injection for Aurelia 1 components.
Explicitly configure the bundler to include HTML files using patterns like `'*.html!text'`. For dynamically generated views, ensure the bundling configuration is aware of their paths or modify the application to fetch them at runtime rather than relying on bundling.