Alpine.js is a tiny JavaScript framework for adding interactivity to a page without building a full single-page app. No build step, no bundler, no framework to learn. You drop one script tag into your HTML, write a few attributes, and your page has dropdowns, modals, tabs, and live counters. If you have ever thought "I just need a little JavaScript here," Alpine is the tool for that.
The idea is simple: Alpine brings the reactive, declarative style of Vue to plain HTML. You write x-data to hold state, x-on:click to handle events, and x-show to toggle visibility. The HTML stays readable, and the JavaScript stays tiny.
<script defer src="https://cdn.jsdelivr.net/npm/alpinejs@3.x.x/dist/cdn.min.js"></script>
<div x-data="{ open: false }">
<button x-on:click="open = !open">Toggle menu</button>
<div x-show="open">
<p>This menu appears and disappears.</p>
</div>
</div>
<div x-data="{ count: 0 }">
<button x-on:click="count++">Clicked <span x-text="count"></span> times</button>
</div>
Getting started takes about two minutes. Add the script tag, write one x-data block, and refresh the page. There is nothing to install, nothing to compile, and the official docs are short enough to read in an evening.
Alpine.js is for beginners who find React overwhelming, backend developers who need a little frontend magic on a server-rendered page, and anyone maintaining a plain HTML site that needs dropdowns, tabs, and forms. It pairs beautifully with Laravel, Django, Rails, and plain PHP.
The limits are honest. Alpine is not for large single-page apps — that is React or Vue territory. Complex state, routing, and big component trees get messy fast, and the ecosystem of ready-made components is small compared to the big frameworks.
Start today with one thing: take any plain HTML page you have and add a working dropdown menu with Alpine. No build step, no npm, just one script tag. In a week you will have added interactivity to every static page you own — and you will wonder why you ever reached for a framework for the small stuff.
Top comments (1)
Small client-side interactions stay maintainable when their lifecycle is explicit. I’d encourage readers to define the initial state in markup, keep server-rendered fallback behavior intact, and test keyboard, focus, and disabled states alongside the happy path. Fifteen lines can be a great boundary if they do not quietly create a second source of truth.