Caution
This project is in early development.
Features and APIs may change.
This document currently outlines the roadmap, not the finalized product.
Holypack is a production-focused build system for scalable, accessible web applications. It begins with minimal setup, builds on strong defaults, and incorporates best practices like linting, testing, and security to support modern, backend-agnostic workflows.
Most build tools are either tightly coupled to a specific backend (often JavaScript or TypeScript) or overlook progressive enhancement, which is essential for accessibility and long-term resilience.
Holypack addresses both. It supports backend independence and fast delivery without compromising quality. Its scope is defined by the intersection of these priorities. No rigid architectures, no loss of flexibility.
While developer experience matters, holypack is ultimately optimized for production: What reaches the user is the true measure of quality.
- Production-ready: Reliable output with minimal setup
- Guided flexibility: Balances "convention" and "configuration"
- Workflow-aware: Compatible with modern developer tooling
- Proven foundations: Built on stable, trusted technologies
- Unopinionated: Fits diverse project structures without constraints
Holypack combines battle-tested tools and proven technologies to achieve high-quality outcomes in modern web development.
- Assets-only (For monolithic backends)
- Single Page Applications (SPA)
- Progressive Web Applications (PWA) with service workers and navigation preloading
- Server-Side Rendering (SSR) with progressive enhancement
- Code and asset bundling via webpack
- JavaScript/TypeScript transpilation with Babel and SWC
- CSS processing with PostCSS and Lightning CSS
- Superpowered CSS, with Sass and SCSS
- First-class CSS modules support
- Code style standardization with ESLint, axe-core and Stylelint
- Unit testing with Jest and coverage by Istanbul
- Subresource Integrity (SRI)
- Content Security Policy (CSP)
- Trusted Types
- Dual builds for modern and legacy environments
- Built-in support for graceful degradation
- Build CLI applications targeting Node.js (including SSR use cases)
- Optional JavaScript obfuscation for closed-source projects
- Support for generating single-file executables
Warning
Code obfuscation is not a security mechanism for intellectual properties. It serves as a deterrent and may support legal standing by demonstrating that violations were deliberate rather than accidental.
| Name | Package | Status |
|---|---|---|
| | ||
| Linters | ||
| ESLint | @holypack/integration-eslint | Completed |
| axe-core | Planned | |
| Stylelint | Planned | |
| commitlint | Planned | |
| Husky | Planned | |
| | ||
| Build Tools | ||
| TypeScript | @holypack/integration-typescript | Completed |
| Babel | @holypack/integration-babel | Completed |
| SWC | Planned | |
| JavaScript Obfuscator | Planned | |
| PostCSS | Planned | |
| Lightning CSS | Planned | |
| Sass | Planned | |
| SCSS | Planned | |
| Browserslist | Planned | |
| webpack | @holypack/integration-webpack | Work in progress |
| | ||
| Testing Tools | ||
| Jest | @holypack/integration-jest | Completed |
| | ||
| Distribution & Release Tools | ||
| changesets | Planned | |
| export-map-generator | Completed | |
| | ||
| Libraries & Frameworks | ||
| Express | Planned | |
| React | Planned | |
| | ||
| Polyfills | ||
| core-js | Planned | |
| trusted-types | Planned | |
| Name | Package | Status |
|---|---|---|
| core | @holypack/core | Completed |
| cli | @holypack/cli | Work in progress |
| prelude | holypack | Completed |
The packages will be available once the initial implementation is complete.
The final view of the usage will be provided at a later stage.
The name began as a reaction to how crowded the npm registry felt. Over time, it became a reflection of the technologies and principles behind the project. Also, cats are very surprising.
Like webpack, holypack is not capitalized mid-sentence.
This project is licensed under the MIT License. See the LICENSE file for more information.