PHPackages                             marko/vite - 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. [Framework](/categories/framework)
4. /
5. marko/vite

ActiveMarko-module[Framework](/categories/framework)

marko/vite
==========

Vite integration for the Marko Framework - asset manifest resolution and dev-server detection

0.8.4(2mo ago)078↓50%4MITPHPPHP ^8.5

Since May 1Pushed 1mo agoCompare

[ Source](https://github.com/marko-php/marko-vite)[ Packagist](https://packagist.org/packages/marko/vite)[ RSS](/packages/marko-vite/feed)WikiDiscussions main Synced 3w ago

READMEChangelogDependencies (6)Versions (14)Used By (4)

marko/vite
==========

[](#markovite)

Vite integration for the Marko Framework — asset manifest resolution and dev-server detection for production builds and HMR.

Installation
------------

[](#installation)

```
composer require marko/vite
```

Quick Example
-------------

[](#quick-example)

```
use Marko\Vite\Vite;

class LayoutController
{
    public function __construct(
        private readonly Vite $vite,
    ) {}

    public function head(): string
    {
        return $this->vite->headTags('app/web/resources/js/app.js');
    }
}
```

In dev (`vite.useDevServer = true`), this emits `` tags pointing at the Vite dev server. In production, it reads `public/build/.vite/manifest.json` and emits hashed ``, ``, and `` tags.

Documentation
-------------

[](#documentation)

Full usage, API reference, and examples: [marko/vite](https://marko.build/docs/packages/vite/)

###  Health Score

42

—

FairBetter than 88% of packages

Maintenance89

Actively maintained with recent releases

Popularity10

Limited adoption so far

Community13

Small or concentrated contributor base

Maturity49

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 50% 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 ~0 days

Total

12

Last Release

84d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/437029?v=4)[Mark Shust](/maintainers/markshust)[@markshust](https://github.com/markshust)

---

Top Contributors

[![markshust](https://avatars.githubusercontent.com/u/437029?v=4)](https://github.com/markshust "markshust (1 commits)")[![ps-carvalho](https://avatars.githubusercontent.com/u/65711196?v=4)](https://github.com/ps-carvalho "ps-carvalho (1 commits)")

### Embed Badge

![Health badge](/badges/marko-vite/health.svg)

```
[![Health](https://phpackages.com/badges/marko-vite/health.svg)](https://phpackages.com/packages/marko-vite)
```

PHPackages © 2026

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