PHPackages                             faslatam/alpine-js - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. faslatam/alpine-js

ActiveLibrary[Utility & Helpers](/categories/utility)

faslatam/alpine-js
==================

AlpineJS composer package

3.14.9(1y ago)075MIT

Since Feb 8Pushed 1y ago1 watchersCompare

[ Source](https://github.com/fadrian06/AlpineJS)[ Packagist](https://packagist.org/packages/faslatam/alpine-js)[ RSS](/packages/faslatam-alpine-js/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependenciesVersions (3)Used By (0)

Alpine.js
=========

[](#alpinejs)

Go to the Alpine docs for most things: [Alpine Docs](https://alpinejs.dev)

You are welcome to submit updates to the docs by submitting a PR to this repo. Docs are located in the [`/packages/docs`](/packages/docs) directory.

Stay here for contribution-related information.

> Looking for V2 docs? [here they are](https://github.com/alpinejs/alpine/tree/v2.8.2)

[![Alpine Component Patterns](https://github.com/alpinejs/alpine/raw/main/hero.jpg)](https://alpinejs.dev/patterns)

Contribution Guide:
-------------------

[](#contribution-guide)

### Quickstart

[](#quickstart)

- clone this repo locally
- run `npm install` & `npm run build`
- Include the `/packages/alpinejs/dist/cdn.js` file from a `` tag on a webpage and you're good to go!

### Brief Tour

[](#brief-tour)

You can get everything installed with: `npm install` in the root directory of this repo after cloning it locally.

This repo is a "mono-repo" using npm workspaces for managing the packages. Each package has its own folder in the `/packages` directory.

Rather than having to run separate builds for each package, all package bundles are handled with the same command: `npm run build`

Here's a brief look at each package in this repo:

PackageDescription[alpinejs](packages/alpinejs)The main Alpine repo with all of Alpine's core[collapse](packages/collapse)A plugin for expanding and collapsing elements using smooth animations[csp](packages/csp)A repo to provide a "CSP safe" build of Alpine[docs](packages/docs)The Alpine documentation[focus](packages/focus)A plugin that allows you to manage focus inside an element[history](packages/history)A plugin for binding data to query string parameters using the history API (name is likely to change)[intersect](packages/intersect)A plugin for triggering JS expressions based on elements intersecting with the viewport[mask](packages/mask)A plugin for automatically formatting a text input field as a user types[morph](packages/morph)A plugin for morphing HTML (like morphdom) inside the page intelligently[persist](packages/persist)A plugin for persisting Alpine state across page loadsThe compiled JS files (as a result of running `npm run [build/watch]`) to be included as a `` tag for example are stored in each package's `packages/[package]/dist` directory.

Each package should at least have: a "cdn" build that is self-initializing and can be included using the `src` attribute in a `` tag, and a `module.[esm/cjs].js` file that is used for importing as a JS module (cjs for node, esm for everything else).

The bundling for Alpine V3 is handled exclusively by ESBuild. All of the configuration for these builds is stored in the `scripts/build.js` file.

### Testing

[](#testing)

There are 2 different testing tools used in this repo: Cypress (for integration tests), and Jest (for unit tests).

All tests are stored inside the `/tests` folder under `/tests/cypress` and `/tests/jest`.

You can run them both from the command line using: `npm run test`

If you wish to only run cypress and open it's user interface (recommended during development), you can run: `npm run cypress`

If you wish to only run Jest tests, you can run `npm run jest` like normal and target specific tests. You can specify command line config options to forward to the jest command with `--` like so: `npm run jest -- --watch`

###  Health Score

27

—

LowBetter than 49% of packages

Maintenance47

Moderate activity, may be stable

Popularity9

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity39

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~32 days

Total

2

Last Release

422d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/37f9864d589abf634aa9a44b9aec1f644adf3104e01812da202ac4c1c860957d?d=identicon)[fadrian06](/maintainers/fadrian06)

---

Top Contributors

[![fadrian06](https://avatars.githubusercontent.com/u/109766973?v=4)](https://github.com/fadrian06 "fadrian06 (5 commits)")

### Embed Badge

![Health badge](/badges/faslatam-alpine-js/health.svg)

```
[![Health](https://phpackages.com/badges/faslatam-alpine-js/health.svg)](https://phpackages.com/packages/faslatam-alpine-js)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)