!Dependency count

stage1

High-performance JavaScript micro framework.

> Warning: This is alpha software. Test thoroughly before using in production. Please report any bugs you find!

Originally a fork of the excellent project.

TODO

- Decide whether to keep multiple implementations
- Browser "live" compile, browser runtime mode
- Bun default precompiled mode
- Bun "fast" precompiled mode (use this as the default implementation and remove "normal" precompiled mode?)
- Downside is the API is different to the other modes (collect function return type)
- Keep only the most used functionality in stage1 and move less used but still useful functionality to stage2
- Should the reactive store be in stage1 or stage2?
- Should less used DOM utilities be moved to stage2?
- prepend
- insert
- replace
- text?
- How much focus should be given to stage1 used as a prebuilt/CDN browser/live package vs a build-time library?
- Maybe we can actually include more functionality when used as a lib but intentionally reduce what's included in the prebuilt browser/live package.
- Add documentation about:
- Security:
- Internal use of innerHTML — potential risk of XSS etc.; never use h and html functions with untrusted input
- In future we may have Sanitizer.sanitizeFor(...) which could be used to sanitize untrusted input
- It's unlikely we'll use it internally due to performance overhead but developers should definitely sanitize input when untrusted before passing it in... although we could create light wrapper functions
-
-
- New DOM utility functions
- fragment
- text
- create
- clone
- append
- prepend
- insert
- replace
- onRemove
- New reactive store feature
- Differences from the original stage0 project:
- There are now 3 runtime modes:
- New precompiled runtime mode and a fast variant for ultimate performance. Compiles templates at build-time via a bun macro that minifies templates, generates metadata, and then includes minimal runtime code in your JS bundle. Currently only works with Bun.build.
- The fast mode is a variant of the precompiled mode that uses a different API and is further optimized for performance.
- The regular mode is still available which generates metadata when your JS is run in the browser. Regular mode can be used with or without a build process.
- Ref nodes are now marked with @ rather than #
- h is now function h(template: string): S1Node e.g., h('

@key

')
- html is available to use as a string template literal tag function e.g., ` html

@key

(regular mode only)
- view.collect is now a collect function that needs to be imported separately
- Extra DOM utils
- New reactive store factory can be imported from stage1/store
- Improved TypeScript support
- Reduced size and improved load and runtime performance
- Import paths:
- Other than reconcilers and the store, everything is a named export from stage1
- Reconcilers all export a reconcile function
- /keyed --> /reconcile/keyed
- /reconcile --> /reconcile/non-keyed
- /reuse-nodes --> /reconcile/reuse-nodes
- Ref names must be lowercase because some browsers normalize element attribute names when rendering HTML
- Note: No longer the case in "fast" mode (different API).
- Comments may be used as refs
- Add API and usage documentation
- The regular mode h() function does not support skipping minification in whitespace sensitive HTML blocks like

 and  because it would be too slow. The precompiled mode compile() macro does however. Same for the other compile options.
- Add more tests
- Add examples
- Set up benchmarking + compare to stage0 and other JS frameworks
- Submit to 
Browser support
> Note: Internet Explorer is not supported.
Minimum browser version required:
- Chrome 26
- Edge 13
- Firefox 22
- Safari 8
- Opera 15
If using the browser runtime mode or synthetic click events:
- Chrome 38
- Edge 13
- Firefox 36
- Safari 9
- Opera 25
Some optional features require a higher browser version:
- html tagged template literal function uses String.raw; requirements
- onRemove utility function uses for...of and MutationObserver; requirements, requirements
  - NOTE: Moved to stage2 package
- store uses Proxy`; requirements
  - Also uses logical nullish assignment>) and optional chaining operator, however, build tools can transform these for old browser targets
SSR (server-side rendering) is not supported and is not the intended use of this library.
Build environment JS runtime support
The default precompiled mode runtime requires bun version 1.0.20 or above.
The regular mode browser bundle does not have any specific build requirements.
Bugs
Please report any bugs you encounter on the GitHub issue tracker.
Changelog
See releases on GitHub.
License
MIT license. See LICENSE.
---
© 2025 Max Milton