µJS, a 5KB alternative to Htmx and Turbo with zero dependencies

I built µJS because I wanted AJAX navigation without the verbosity of HTMX or the overhead of Turbo.It intercepts links and form submissions, fetches pages via AJAX, and swaps fragments of the DOM. Single <script> tag, one call to `mu.init()`. No build step, no dependencies.Key features: patch mode (update multiple fragments in one request), SSE support, DOM morphing via idiomorph, View Transitions, prefetch on hover, polling, and full HTTP verb support on any element.At ~5KB gzipped, it's smaller than HTMX (16KB) and Turbo (25KB), and works with any backend: PHP, Python, Go, Ruby, whatever.Playground: https://mujs.org/playgroundComparison with HTMX and Turbo: https://mujs.org/comparisonAbout the project creation, why and when: https://mujs.org/aboutGitHub: https://github.com/Digicreon/muJSHappy to discuss the project.

Hacker NewsToolDesign & CreativeSource
0Sign in to voteCopy link

FL score

78

out of 100

Verdict

BUILD

high confidence

Competition

9

competitors found, emerging market

Trend

No signal yet

µJS is a compelling, ultra-lightweight, zero-dependency alternative to HTMX/Turbo for developers seeking simpler AJAX navigation, with strong technical merit but a challenging monetization path as a solo builder.

The pain

Developers using existing hypermedia tools like HTMX and Turbo experience significant frustrations with verbosity, overhead, complexity in larger projects ('convoluted mess,' 'spaghetti-like interactions'), and often underestimated performance implications due to excessive HTTP requests.

The gap

While many open-source hypermedia libraries exist, there is a clear demand for an extremely minimalist solution that offers core AJAX navigation and DOM swapping without the 16-25KB overhead and verbosity of HTMX/Turbo, all while maintaining zero dependencies and advanced features like patch mode and SSE support.

Build angle

Build a 5KB, zero-dependency JavaScript library that provides efficient AJAX navigation, DOM fragment swapping, patch mode for multiple updates, SSE, and View Transitions, specifically targeting developers frustrated by the complexity and size of HTMX and Turbo.

Strengths

  • Clear and validated pain point among developers.
  • Highly differentiated product (5KB, zero dependencies, specific feature set like patch mode).
  • Strong creator fit and technical expertise (already built the MVP).
  • Targets a growing market trend towards simpler, performant web development.
  • Easy to understand value proposition and quick integration.
  • Low build complexity for the core product.

Risks

  • Monetization challenge: core library is expected to be free in an open-source dominated market.
  • High developer effort required for adoption of a new tool in a crowded (though non-funded) space.
  • Limited inherent business leverage (network effects, data moats) as an open-source library.
  • Accessibility concerns might be overlooked, as with some competitors.
  • Requires significant community building and evangelism by a solo builder to gain widespread adoption.

Next steps

  1. Deeply engage with the existing HTMX/Turbo communities to validate specific complaints and gather feature requests for a paid offering or commercial support.
  2. Explore specific monetization strategies beyond the core free library (e.g., premium components, dev tools, commercial licenses for enterprises, consulting services, advanced tutorials/courses).
  3. Focus marketing on the unique 5KB / zero-dependency angle and specific use cases where this offers a significant advantage (e.g., extremely performance-sensitive apps, embedded systems, micro frontends).
  4. Gather user testimonials and case studies demonstrating the performance and simplicity benefits in real-world projects.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “µJS, a 5KB alternative to Htmx and Turbo with zero dependencies”.

Open FlyBot