Vite Plugin

Evolving AEM Vite has always and is a primary goal of the project. To ensure AEM Vite keeps up with ever-changing updates and feature inclusions within the Vite ecosystem we are providing a plugin that solves many challenges.

Solving Challenges

In the past, AEM Vite relied heavily on Java to maintain the relationship between ClientLibs and the Vite DevServer. While this worked, it was simply a stop gap to solve the immediate issue of how do we get Vite working nicely in AEM. The @aem-vite/vite-aem-plugin package was born from this initial idea with the goal of eliminating some of the backend set up and introducing something more digestable for front end developers.

This Vite plugin reduces the complexity of the set up, but it couples more of the configuration to a central. Providing a richer and simplified DX (Developer Experience) overall was always the goal, and by relying more on Vite as the underpinning driving force it enables more possibilities than the previous Java implementation could have hoped to achieve.

In addition to these points, this plugin also aims to bring some boilerplate along with it that continues to help simplify installation and set up.

Installation

Getting started is quick and simple. Run the below command to install the Vite AEM plugin.

npm

npm install -D @aem-vite/vite-aem-plugin

pnpm

pnpm add -D @aem-vite/vite-aem-plugin

yarn

yarn add -D @aem-vite/vite-aem-plugin

bun

bun add -D @aem-vite/vite-aem-plugin

Configuration

import { viteForAem } from '@aem-vite/vite-aem-plugin'; 

export default defineConfig(() => ({
  plugins: [
    viteForAem({ 
      contentPaths: ['<content path(s)>'], 
      publicPath: '/etc.clientlibs/<project>/clientlibs/clientlib-site', 
    }), 
  ],
}));

TIP

Refer to the vite configuration and dynamic imports documentation for more information about the publicPath option.

Plugin options

Property Name	Type	Required
aem Set the hostname and port of your AEM instance.	object	No
contentPaths A list of content paths (excluding /content/) to match ClientLib paths in.	array	Yes
publicPath The AEM proxy path to your ClientLib directory.	string	Yes
rewriterOptions Enables the @aem-vite/import-rewriter plugin	object	No

NOTE

The publicPath option is automatically forwarded onto the import rewriter from @aem-vite/vite-aem-plugin.

Usage

This step couldn't be more simple. Run either the serve or build command for Vite and everything will work like magic.

serve

vite serve

build

vite build

By default, @aem-vite/vite-aem-plugin enforces strict port mode when using the Vite DevServer. This will automatically jump to the next available port if 3000 is unavailable.

Content path examples

The following are example paths in AEM:

• /content/<project_one>/en/au
• /content/<project_one>/en/us
• /content/<project_one>/en/es
• /content/<project_two>/en/us/support

There are two ways that path matching is applied:

1. Partially using the root content node name
2. Partially using a path segment below the root node

To match only the US path in project one and everything in Project Two we can use the following list.

{
  contentPaths: [
    '<project_one>/en/us',
    '<project_two>',
  ],
}

WARNING

Adding slashes to the start or end of these paths will cause in the proxy matcher to fail and respond with 404 page served by Vite.

React Support

Whenever the @vitejs/plugin-react plugin is detected, the AEM Vite plugin will automatically inject the React fast refresh script.