PHPackages                             networkteam/neos-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. [Utility & Helpers](/categories/utility)
4. /
5. networkteam/neos-vite

ActiveNeos-package[Utility & Helpers](/categories/utility)

networkteam/neos-vite
=====================

Integrate Vite for asset bundling into Neos CMS

1.0.0(11mo ago)25.0k↓74.2%2[1 PRs](https://github.com/networkteam/Networkteam.Neos.Vite/pulls)MITPHPCI passing

Since Apr 5Pushed 11mo ago1 watchersCompare

[ Source](https://github.com/networkteam/Networkteam.Neos.Vite)[ Packagist](https://packagist.org/packages/networkteam/neos-vite)[ RSS](/packages/networkteam-neos-vite/feed)WikiDiscussions main Synced yesterday

READMEChangelog (6)Dependencies (2)Versions (11)Used By (0)

Networkteam.Neos.Vite
=====================

[](#networkteamneosvite)

Compatibility
-------------

[](#compatibility)

NeosCMSPlugin>= 9.01.x8.x0.3.xInstallation
------------

[](#installation)

Go to your site package:

```
cd DistributionPackages/Your.Site
```

### 1. Install the package via composer

[](#1-install-the-package-via-composer)

```
composer require networkteam/neos-vite
```

### 2. Install Vite via NPM (or Yarn, pnpm):

[](#2-install-vite-via-npm-or-yarn-pnpm)

```
npm install --save-dev vite
```

### 3. Create a `vite.config.mjs` file in your site package:

[](#3-create-a-viteconfigmjs-file-in-your-site-package)

```
import { defineConfig } from "vite";

export default defineConfig((configEnv) => ({
  base: "./",
  build: {
    // generate .vite/manifest.json in outDir
    manifest: true,
    rollupOptions: {
      // overwrite default .html entry
      input: {
        footer: "Resources/Private/Javascript/footer.js",
        header: "Resources/Private/Javascript/header.js",
      },
      output: {
        // The Flowpack.CacheBuster package adds a `?bust` get parameter with a hash based on the file content.
        // This leads to issues with files imported from the manifest, as they may be loaded twice.
        // (Once with the bust parameter and once without, as they are technically two different URLs.)
        // To work around this we add a "bust" infix so CacheBuster skips adding the bust parameter.
        entryFileNames: "assets/[name]-bust-[hash].js",
        // If you use this output option the Fusion object will just work™️
        dir: "Resources/Public/Dist",
      },
    },
  },
}));
```

### 4. You can now include Vite assets for development / production in your Fusion files:

[](#4-you-can-now-include-vite-assets-for-development--production-in-your-fusion-files)

```
header = Networkteam.Neos.Vite:Asset {
    entry = 'Resources/Private/Javascript/header.js'
}

```

This Fusion object will use a different include based on the FLOW\_CONTEXT:

- Development: Loads entry from development server configured for the site (defaults to )
- Production: Based on the generated manifest file it will include the hashed assets with CSS and recursive imports

By default the manifest is expected in `Resources/Public/Dist`, but that can be changed by overriding Fusion properties:

```
prototype(Networkteam.Neos.Vite:Asset) {
    // ...

    outputPathPattern = 'resource://{sitePackageKey}/Public/Dist'
    manifest = '.vite/manifest.json'
}

```

### Bonus: You can generate the URL to entries in the manifest

[](#bonus-you-can-generate-the-url-to-entries-in-the-manifest)

This will only return the URL to the file for an entry without considering imports.

Example for an SVG spritemap (using [vite-plugin-svg-spritemap](https://github.com/SpiriitLabs/vite-plugin-svg-spritemap)):

```
src = Networkteam.Neos.Vite:AssetUrl {
    entry = 'spritemap.svg'
}

```

Multi-site
----------

[](#multi-site)

Configure individual Vite configurations for each site by adding a Vite setup with a corresponding `vite.config.mjs` file in *each* site package. Make sure to run each server on a different port by configuring the `server.port` option in the Vite configuration.

Add Settings for each site in your `Settings.yaml`:

```
Networkteam:
  Neos:
    Vite:
      server:
        # This is the default setting if no configuration part is found for the site package key
        _default:
          url: http://localhost:5173/

        # Specify server configuration for a specific site package key
        MyExample.Site:
          url: http://localhost:5174/
```

Make sure to run multiple Vite servers for each site package.

###  Health Score

37

—

LowBetter than 81% of packages

Maintenance52

Moderate activity, may be stable

Popularity27

Limited adoption so far

Community13

Small or concentrated contributor base

Maturity48

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 76% 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 ~120 days

Total

5

Last Release

337d ago

Major Versions

0.3.1 → 1.0.02025-07-31

### Community

Maintainers

![](https://www.gravatar.com/avatar/7cbf52f8dce27737b73b79ac2c958434339f3dcf704b17a040956ed9a33eb4ef?d=identicon)[networkteam](/maintainers/networkteam)

---

Top Contributors

[![hlubek](https://avatars.githubusercontent.com/u/33351?v=4)](https://github.com/hlubek "hlubek (19 commits)")[![lneugebauer](https://avatars.githubusercontent.com/u/25110308?v=4)](https://github.com/lneugebauer "lneugebauer (4 commits)")[![jonaphil](https://avatars.githubusercontent.com/u/187416060?v=4)](https://github.com/jonaphil "jonaphil (1 commits)")[![Rasmizzle](https://avatars.githubusercontent.com/u/47476377?v=4)](https://github.com/Rasmizzle "Rasmizzle (1 commits)")

### Embed Badge

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

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

###  Alternatives

[neos/seo

SEO configuration and tools for Neos

141.0M31](/packages/neos-seo)[sitegeist/kaleidoscope

Responsive-images for Neos

29370.3k12](/packages/sitegeist-kaleidoscope)[kaufmanndigital/gdpr-cookieconsent

A ready-to-run package, that integrates an advanced cookie consent banner into your Neos CMS site.

2542.4k](/packages/kaufmanndigital-gdpr-cookieconsent)[techdivision/ckstyles

Neos package which enables you adding your custom style classes for the CkEditor with a simple Yaml configuration

21179.5k](/packages/techdivision-ckstyles)[sitegeist/taxonomy

Manage vocabularies and taxonomies as separate node-hierarchy.

1595.1k1](/packages/sitegeist-taxonomy)[shel/neos-colorpicker

A plugin for Neos CMS which provides a colorpicker editor

14104.7k6](/packages/shel-neos-colorpicker)

PHPackages © 2026

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