### Configure pnpm with frontend-maven-plugin

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Shows the setup for installing Node.js and pnpm, followed by executing package installation and test phases within the Maven build process.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <installDirectory>target</installDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install node and pnpm</id>
            <goals>
                <goal>install-node-and-pnpm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
                <pnpmVersion>v10.26.1</pnpmVersion>
            </configuration>
        </execution>
        <execution>
            <id>pnpm install</id>
            <goals>
                <goal>pnpm</goal>
            </goals>
            <configuration>
                <arguments>install</arguments>
            </configuration>
        </execution>
        <execution>
            <id>pnpm test</id>
            <goals>
                <goal>pnpm</goal>
            </goals>
            <phase>test</phase>
            <configuration>
                <arguments>test</arguments>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Running Bun Install with Frontend Maven Plugin

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configures the frontend-maven-plugin to execute a Bun installation command. The goal is set to 'bun', and the 'install' argument is specified. This is typically performed during the 'generate-resources' phase.

```xml
<execution>
    <id>bun install</id>
    <goals>
        <goal>bun</goal>
    </goals>

    <phase>generate-resources</phase>

    <configuration>
        <arguments>install</arguments>
    </configuration>
</execution>
```

--------------------------------

### Install Node.js/npm and Run Gulp with Frontend Maven Plugin

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Integrates Node.js and npm installation with the frontend-maven-plugin, followed by Gulp task execution. This setup supports incremental builds by defining source and output directories for Gulp tasks.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
            </configuration>
        </execution>
        <execution>
            <id>npm install</id>
            <goals>
                <goal>npm</goal>
            </goals>
        </execution>
        <execution>
            <id>gulp build</id>
            <goals>
                <goal>gulp</goal>
            </goals>
            <phase>generate-resources</phase>
            <configuration>
                <!-- Gulp task to run (optional, defaults to default task) -->
                <arguments>build</arguments>
                <!-- Source directory for incremental build detection (optional) -->
                <srcdir>src/main/frontend</srcdir>
                <!-- Output directory to refresh in Eclipse (optional) -->
                <outputdir>target/frontend</outputdir>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Configure Yarn with frontend-maven-plugin

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Demonstrates how to install Node.js and Yarn, then execute install and build commands. It includes optional configurations for private registries and proxy settings.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <installDirectory>target</installDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install node and yarn</id>
            <goals>
                <goal>install-node-and-yarn</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
                <yarnVersion>v1.22.22</yarnVersion>
            </configuration>
        </execution>
        <execution>
            <id>yarn install</id>
            <goals>
                <goal>yarn</goal>
            </goals>
            <configuration>
                <arguments>install</arguments>
                <npmRegistryURL>https://registry.example.com/</npmRegistryURL>
                <yarnInheritsProxyConfigFromMaven>false</yarnInheritsProxyConfigFromMaven>
            </configuration>
        </execution>
        <execution>
            <id>yarn build</id>
            <goals>
                <goal>yarn</goal>
            </goals>
            <configuration>
                <arguments>build</arguments>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Configuring Installation Directory for Frontend Maven Plugin

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Specifies the directory where Node.js and npm will be installed by the frontend-maven-plugin. This configuration can be applied globally within the plugin's main configuration or per goal. The example shows a global setting.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>

    <configuration>
        <installDirectory>target</installDirectory>
    </configuration>
</plugin>
```

--------------------------------

### Configure Bun Installation

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configures the plugin to download and install a specific version of the Bun runtime locally to the project.

```xml
<plugin>
    <executions>
        <execution>
            <id>install bun</id>
            <goals>
                <goal>install-bun</goal>
            </goals>
            <phase>generate-resources</phase>
        </execution>
    </executions>
    <configuration>
        <bunVersion>v1.1.34</bunVersion>
    </configuration>
</plugin>
```

--------------------------------

### Install Node.js and npm with Maven

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

This snippet configures the frontend-maven-plugin to download and install a specific version of Node.js and npm locally for the project. It's typically run during the 'generate-resources' phase. Dependencies include the plugin itself and specified Node/npm versions. Inputs are configuration parameters like nodeVersion and npmVersion. Outputs are local installations of Node.js and npm.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <phase>generate-resources</phase>
            <configuration>
                <!-- Node.js version to install (required) -->
                <nodeVersion>v24.12.0</nodeVersion>
                <!-- npm version (optional, defaults to version bundled with Node) -->
                <npmVersion>11.6.2</npmVersion>
                <!-- Custom download location (optional) -->
                <nodeDownloadRoot>https://nodejs.org/dist/</nodeDownloadRoot>
                <npmDownloadRoot>https://registry.npmjs.org/npm/-/</npmDownloadRoot>
                <!-- Maven server ID for authentication (optional) -->
                <serverId>my-node-server</serverId>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Install Bun Runtime

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Configures the plugin to install the Bun runtime locally within the project directory. This enables fast execution and bundling of JavaScript and TypeScript projects.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <installDirectory>target</installDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install bun</id>
            <goals>
                <goal>install-bun</goal>
            </goals>
            <configuration>
                <bunVersion>v1.3.5</bunVersion>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Execute JSPM Installation

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configuring the plugin to run jspm install, which manages dependencies in the jspm_packages directory.

```xml
<execution>
    <id>jspm install</id>
    <goals>
        <goal>jspm</goal>
    </goals>
    <configuration>
        <arguments>install</arguments>
    </configuration>
</execution>
```

--------------------------------

### Install and Run Bun with Frontend Maven Plugin

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Configures the frontend-maven-plugin to install a specific version of Bun and execute Bun commands. This is useful for managing JavaScript/TypeScript packages and running scripts efficiently.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <installDirectory>target</installDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install bun</id>
            <goals>
                <goal>install-bun</goal>
            </goals>
            <configuration>
                <bunVersion>v1.3.5</bunVersion>
            </configuration>
        </execution>
        <execution>
            <id>bun install</id>
            <goals>
                <goal>bun</goal>
            </goals>
            <configuration>
                <arguments>install</arguments>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Configure Custom Installation Directory

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

This snippet configures the plugin to install Node and npm into a specific directory, such as the target folder, which is useful for clean build environments.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <installDirectory>target</installDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Configure Node.js and npm installation

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configures the plugin to download and install specific versions of Node.js and npm locally. It supports custom download roots and proxy configurations.

```xml
<plugin>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <phase>generate-resources</phase>
        </execution>
    </executions>
    <configuration>
        <nodeVersion>v24.12.0</nodeVersion>
        <npmVersion>11.6.2</npmVersion>
        <downloadRoot>http://myproxy.example.org/nodejs/</downloadRoot>
    </configuration>
</plugin>
```

--------------------------------

### Execute npm and npx Commands

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Demonstrates how to run npm install or execute arbitrary packages using npx within the Maven build lifecycle.

```xml
<execution>
    <id>npm install</id>
    <goals>
        <goal>npm</goal>
    </goals>
    <phase>generate-resources</phase>
    <configuration>
        <arguments>install</arguments>
    </configuration>
</execution>

<execution>
    <id>say hello</id>
    <goals>
        <goal>npx</goal>
    </goals>
    <phase>generate-resources</phase>
    <configuration>
        <arguments>cowsay hello</arguments>
    </configuration>
</execution>
```

--------------------------------

### Install Node.js/npm and Run Grunt with Frontend Maven Plugin

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Sets up Node.js and npm using the frontend-maven-plugin, then executes Grunt tasks. This configuration allows for incremental builds and specifies directories for source and output, along with trigger files for rebuild detection.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
            </configuration>
        </execution>
        <execution>
            <id>npm install</id>
            <goals>
                <goal>npm</goal>
            </goals>
        </execution>
        <execution>
            <id>grunt build</id>
            <goals>
                <goal>grunt</goal>
            </goals>
            <phase>generate-resources</phase>
            <configuration>
                <!-- Grunt task to run (optional, defaults to default task) -->
                <arguments>build</arguments>
                <!-- Source directory for incremental build detection (optional) -->
                <srcdir>src/main/frontend</srcdir>
                <!-- Output directory to refresh in Eclipse (optional) -->
                <outputdir>target/frontend</outputdir>
                <!-- Additional trigger files for rebuild detection (optional) -->
                <triggerfiles>
                    <triggerfile>Gruntfile.js</triggerfile>
                    <triggerfile>package.json</triggerfile>
                </triggerfiles>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Install Node.js and Corepack

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Configures the plugin to download and install a specific version of Node.js and Corepack. Corepack allows for seamless management of package managers like Yarn and pnpm.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <installDirectory>target</installDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install node and corepack</id>
            <goals>
                <goal>install-node-and-corepack</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
                <corepackVersion>0.25.2</corepackVersion>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Configure Frontend Maven Plugin for Fullstack Builds

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

This XML configuration demonstrates how to install Node.js and npm, run dependency installation, execute linting, perform unit tests, and build the frontend assets within a Maven project. It also includes a resource plugin step to copy the final build artifacts into the Spring Boot static folder.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <workingDirectory>src/main/frontend</workingDirectory>
        <installDirectory>target</installDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install-node-and-npm</id>
            <goals><goal>install-node-and-npm</goal></goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
                <npmVersion>11.6.2</npmVersion>
            </configuration>
        </execution>
        <execution>
            <id>npm-ci</id>
            <goals><goal>npm</goal></goals>
            <configuration><arguments>ci</arguments></configuration>
        </execution>
        <execution>
            <id>npm-lint</id>
            <goals><goal>npm</goal></goals>
            <phase>process-resources</phase>
            <configuration><arguments>run lint</arguments></configuration>
        </execution>
        <execution>
            <id>npm-test</id>
            <goals><goal>npm</goal></goals>
            <phase>test</phase>
            <configuration>
                <arguments>run test -- --ci --coverage</arguments>
                <environmentVariables><CI>true</CI></environmentVariables>
            </configuration>
        </execution>
        <execution>
            <id>npm-build</id>
            <goals><goal>npm</goal></goals>
            <phase>prepare-package</phase>
            <configuration>
                <arguments>run build</arguments>
                <environmentVariables><NODE_ENV>production</NODE_ENV></environmentVariables>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Install Node.js and Yarn with Maven

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

This configuration installs Node.js and the Yarn package manager locally. It supports both Yarn Classic and Yarn Berry, automatically detecting Yarn Berry if a .yarnrc.yml file is present. The plugin downloads specified versions of Node.js and Yarn, making them available for project builds. Custom download roots can be specified.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <installDirectory>target</installDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install node and yarn</id>
            <goals>
                <goal>install-node-and-yarn</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
                <!-- For Yarn Berry projects, this 1.x version serves as bootstrap -->
                <yarnVersion>v1.22.22</yarnVersion>
                <!-- Custom download locations (optional) -->
                <nodeDownloadRoot>https://nodejs.org/dist/</nodeDownloadRoot>
                <yarnDownloadRoot>https://github.com/yarnpkg/yarn/releases/download/</yarnDownloadRoot>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Configure Node.js and Corepack Installation

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configures the plugin to download and install a specific version of Node.js and Corepack locally. It supports custom download mirrors for environments with restricted internet access.

```xml
<plugin>
    <execution>
        <id>install-node-and-corepack</id>
        <goals>
            <goal>install-node-and-corepack</goal>
        </goals>
        <phase>generate-resources</phase>
    </execution>
    <configuration>
        <nodeVersion>v24.12.0</nodeVersion>
        <corepackVersion>v0.25.2</corepackVersion>
        <nodeDownloadRoot>http://myproxy.example.org/nodejs/</nodeDownloadRoot>
        <corepackDownloadRoot>http://myproxy.example.org/corepack/</corepackDownloadRoot>
    </configuration>
</plugin>
```

--------------------------------

### Configure Webpack Build Execution

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

This snippet demonstrates how to configure the frontend-maven-plugin to run a Webpack build during the generate-resources phase. It includes node installation, dependency installation, and specific Webpack arguments.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
            </configuration>
        </execution>
        <execution>
            <id>npm install</id>
            <goals>
                <goal>npm</goal>
            </goals>
        </execution>
        <execution>
            <id>webpack build</id>
            <goals>
                <goal>webpack</goal>
            </goals>
            <phase>generate-resources</phase>
            <configuration>
                <arguments>--mode production</arguments>
                <srcdir>src/main/frontend</srcdir>
                <outputdir>target/classes/static</outputdir>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Install Node.js and pnpm with Maven

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

This Maven configuration installs Node.js and the pnpm package manager locally. pnpm is known for its speed and disk-space efficiency. The plugin downloads the specified versions of Node.js and pnpm, enabling their use within the Maven build lifecycle for frontend development.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <installDirectory>target</installDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install node and pnpm</id>
            <goals>
                <goal>install-node-and-pnpm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
                <pnpmVersion>v10.26.1</pnpmVersion>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Install Frontend Maven Plugin

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Add the frontend-maven-plugin to your Maven project's pom.xml file to enable Node.js and package manager integration.

```xml
<plugins>
    <plugin>
        <groupId>com.github.eirslett</groupId>
        <artifactId>frontend-maven-plugin</artifactId>
        <version>LATEST_VERSION</version>
    </plugin>
</plugins>
```

--------------------------------

### Configure Node.js and Yarn installation

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configures the plugin to use Yarn as the package manager instead of npm. It supports custom download roots for both Node.js and Yarn binaries.

```xml
<plugin>
    <execution>
        <id>install node and yarn</id>
        <goals>
            <goal>install-node-and-yarn</goal>
        </goals>
        <phase>generate-resources</phase>
    </execution>
    <configuration>
        <nodeVersion>v24.12.0</nodeVersion>
        <yarnVersion>v0.16.1</yarnVersion>
        <nodeDownloadRoot>http://myproxy.example.org/nodejs/</nodeDownloadRoot>
        <yarnDownloadRoot>http://myproxy.example.org/yarn/</yarnDownloadRoot>
    </configuration>
</plugin>
```

--------------------------------

### Execute Bower Dependencies

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Maven configuration to run bower install, which places dependencies into the bower_components directory.

```xml
<execution>
    <id>bower install</id>
    <goals>
        <goal>bower</goal>
    </goals>
    <configuration>
        <arguments>install</arguments>
    </configuration>
</execution>
```

--------------------------------

### Execute npx Binaries

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Configures the plugin to execute npm package binaries via npx. Useful for running tools without requiring them to be installed as local project dependencies.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <installDirectory>target</installDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
                <npmVersion>11.6.2</npmVersion>
            </configuration>
        </execution>
        <execution>
            <id>npx cowsay</id>
            <goals>
                <goal>npx</goal>
            </goals>
            <configuration>
                <arguments>-y cowsay@1.6.0 hello</arguments>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Execute Yarn Commands

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configures the plugin to run yarn commands, such as installing dependencies, during the Maven build process.

```xml
<execution>
    <id>yarn install</id>
    <goals>
        <goal>yarn</goal>
    </goals>
    <configuration>
        <arguments>install</arguments>
    </configuration>
</execution>
```

--------------------------------

### Running Karma Tests with Frontend Maven Plugin

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configures the frontend-maven-plugin to execute Karma tests. It specifies the execution goal as 'karma' and allows customization of the Karma configuration file path. This setup is typically used within the 'test' Maven phase.

```xml
<execution>
    <id>javascript tests</id>
    <goals>
        <goal>karma</goal>
    </goals>

    <phase>test</phase>

    <configuration>
        <karmaConfPath>src/test/javascript/karma.conf.ci.js</karmaConfPath>
    </configuration>
</execution>
```

--------------------------------

### Configure custom download roots and authentication

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Demonstrates how to specify separate download repositories for Node.js and npm, including using server credentials from the Maven settings file.

```xml
<plugin>
    <configuration>
        <nodeDownloadRoot>http://myproxy.example.org/nodejs/</nodeDownloadRoot>
        <serverId>server001</serverId>
        <npmDownloadRoot>https://myproxy.example.org/npm/</npmDownloadRoot>
    </configuration>
</plugin>
```

--------------------------------

### Execute npm Commands

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Demonstrates how to run standard npm commands like ci, test, and build within the Maven lifecycle. It supports custom registry URLs and proxy configuration overrides.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
            </configuration>
        </execution>
        <execution>
            <id>npm ci</id>
            <goals>
                <goal>npm</goal>
            </goals>
            <configuration>
                <arguments>ci</arguments>
            </configuration>
        </execution>
        <execution>
            <id>npm test</id>
            <goals>
                <goal>npm</goal>
            </goals>
            <phase>test</phase>
            <configuration>
                <arguments>run test</arguments>
            </configuration>
        </execution>
        <execution>
            <id>npm build</id>
            <goals>
                <goal>npm</goal>
            </goals>
            <configuration>
                <arguments>run build</arguments>
                <npmRegistryURL>https://registry.example.com/</npmRegistryURL>
                <npmInheritsProxyConfigFromMaven>false</npmInheritsProxyConfigFromMaven>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Configure Environment Variables for Node

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Demonstrates how to pass custom environment variables to Node.js executions, including support for static values and dynamic Maven properties.

```xml
<configuration>
    <environmentVariables>
        <Jon>Snow</Jon>
        <Tyrion>Lannister</Tyrion>
        <NODE_ENV>${NODE_ENV}</NODE_ENV>
    </environmentVariables>
</configuration>
```

--------------------------------

### Skip Frontend Plugin Goals (XML and Command Line)

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Demonstrates how to skip specific goals of the frontend-maven-plugin during a Maven build. This can be achieved by configuring skip properties within the pom.xml or by using system properties on the command line. This helps in controlling which parts of the frontend build process are executed.

```xml
<!-- In pom.xml -->
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
            </configuration>
        </execution>
        <execution>
            <id>npm install</id>
            <goals>
                <goal>npm</goal>
            </goals>
        </execution>
    </executions>
</plugin>

<!-- Skip via command line -->
<!-- mvn install -Dskip.installnodenpm -Dskip.npm -->
<!--
Available skip properties:
  -Dskip.installnodenpm     Skip install-node-and-npm
  -Dskip.installyarn        Skip install-node-and-yarn
  -Dskip.installnodepnpm    Skip install-node-and-pnpm
  -Dskip.installnodecorepack Skip install-node-and-corepack
  -Dskip.installbun         Skip install-bun
  -Dskip.npm                Skip npm
  -Dskip.npx                Skip npx
  -Dskip.yarn               Skip yarn
  -Dskip.pnpm               Skip pnpm
  -Dskip.corepack           Skip corepack
  -Dskip.bun                Skip bun
  -Dskip.grunt              Skip grunt
  -Dskip.gulp               Skip gulp
  -Dskip.webpack            Skip webpack
  -Dskip.karma              Skip karma
-->
```

--------------------------------

### Configure Custom Working Directory

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

This snippet demonstrates how to set a specific working directory for the frontend project, ensuring the plugin looks for package.json in the correct subfolder.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <workingDirectory>src/main/frontend</workingDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
                <npmVersion>11.6.2</npmVersion>
            </configuration>
        </execution>
        <execution>
            <id>npm ci</id>
            <goals>
                <goal>npm</goal>
            </goals>
            <configuration>
                <arguments>ci</arguments>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Configure Grunt or Gulp Build Directories

Source: https://github.com/eirslett/frontend-maven-plugin/wiki/Home

Configures source and output directories along with trigger files for incremental builds in M2Eclipse. These settings help the plugin track changes to files like gulpfile.js or package.json.

```xml
<configuration>
  <srcdir>${basedir}/src/main/frontend</srcdir>
  <outputdir>${project.build.directory}/frontend</outputdir>
  <triggerfiles>
    <triggerfile>gulpfile.js</triggerfile>
    <triggerfile>package.json</triggerfile>
  </triggerfiles>
</configuration>
```

--------------------------------

### Running Webpack Build with Frontend Maven Plugin

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configures the frontend-maven-plugin to execute a Webpack build. The goal is set to 'webpack', and it can accept arguments for the Webpack command, such as '-p' for production builds. This is often run during the 'generate-resources' phase.

```xml
<execution>
    <id>webpack build</id>
    <goals>
        <goal>webpack</goal>
    </goals>

    <phase>generate-resources</phase>

    <configuration>
        <arguments>-p</arguments>
    </configuration>
</execution>
```

--------------------------------

### Configure Plugin for Maven 2 Compatibility

Source: https://github.com/eirslett/frontend-maven-plugin/wiki/Home

Shows how to configure the plugin for use with Maven 2 by pinning the version to 0.0.22 and adding a dependency on plexus-utils.

```xml
<plugins>
    <plugin>
        <groupId>com.github.eirslett</groupId>
        <artifactId>frontend-maven-plugin</artifactId>
        <version>0.0.22</version>
        <dependencies>
            <dependency>
                <groupId>org.codehaus.plexus</groupId>
                <artifactId>plexus-utils</artifactId>
                <version>2.1</version>
            </dependency>
        </dependencies>
    </plugin>
</plugins>
```

--------------------------------

### Configure Corepack with frontend-maven-plugin

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Explains how to use Corepack to manage package manager versions defined in the project's package.json file. It demonstrates running Yarn and pnpm commands through the Corepack goal.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <configuration>
        <installDirectory>target</installDirectory>
    </configuration>
    <executions>
        <execution>
            <id>install node and corepack</id>
            <goals>
                <goal>install-node-and-corepack</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
            </configuration>
        </execution>
        <execution>
            <id>yarn install via corepack</id>
            <goals>
                <goal>corepack</goal>
            </goals>
            <configuration>
                <arguments>yarn install --no-immutable</arguments>
            </configuration>
        </execution>
        <execution>
            <id>pnpm build via corepack</id>
            <goals>
                <goal>corepack</goal>
            </goals>
            <configuration>
                <arguments>pnpm build</arguments>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Execute Gulp Tasks

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configuring the plugin to run Gulp tasks defined in gulpfile.js during the generate-resources phase.

```xml
<execution>
    <id>gulp build</id>
    <goals>
        <goal>gulp</goal>
    </goals>
    <phase>generate-resources</phase>
    <configuration>
        <arguments>build</arguments>
    </configuration>
</execution>
```

--------------------------------

### Execute Package Managers with Corepack

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configuring the frontend-maven-plugin to execute Yarn or pnpm commands using Corepack.

```xml
<execution>
    <id>install</id>
    <goals>
        <goal>corepack</goal>
    </goals>
    <configuration>
        <arguments>yarn install</arguments>
    </configuration>
</execution>
```

--------------------------------

### Configuring Working Directory for Frontend Maven Plugin

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Sets a custom working directory for the frontend-maven-plugin. This is useful when frontend files (like package.json, Gruntfile.js, or gulpfile.js) are located in a subdirectory other than the project's base directory. The default is the project's root.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>

    <configuration>
        <workingDirectory>src/main/frontend</workingDirectory>
    </configuration>
</plugin>
```

--------------------------------

### Configure Test Failure Handling (XML)

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Configure the frontend-maven-plugin to control how test failures are handled during the Maven build. By setting `testFailureIgnore` to `true`, the build will continue even if frontend tests fail. This is useful for development or when test results do not block the entire build process.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
            </configuration>
        </execution>
        <execution>
            <id>npm test</id>
            <goals>
                <goal>npm</goal>
            </goals>
            <phase>test</phase>
            <configuration>
                <arguments>run test</arguments>
                <!-- Continue build even if tests fail -->
                <testFailureIgnore>true</testFailureIgnore>
            </configuration>
        </execution>
    </executions>
</plugin>

<!-- Skip all tests via command line -->
<!-- mvn install -DskipTests -->
```

--------------------------------

### Execute Grunt Tasks

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configuring the plugin to run Grunt tasks defined in Gruntfile.js during the generate-resources phase.

```xml
<execution>
    <id>grunt build</id>
    <goals>
        <goal>grunt</goal>
    </goals>
    <phase>generate-resources</phase>
    <configuration>
        <arguments>build</arguments>
    </configuration>
</execution>
```

--------------------------------

### Pass Environment Variables to Frontend Commands (XML)

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

Configure the frontend-maven-plugin to pass custom environment variables to frontend build commands. This is useful for setting build-specific configurations like API endpoints or build numbers. Dependencies include the plugin itself and the Maven build environment.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
            </configuration>
        </execution>
        <execution>
            <id>npm build</id>
            <goals>
                <goal>npm</goal>
            </goals>
            <configuration>
                <arguments>run build</arguments>
                <environmentVariables>
                    <NODE_ENV>production</NODE_ENV>
                    <API_URL>${api.url}</API_URL>
                    <BUILD_NUMBER>${build.number}</BUILD_NUMBER>
                </environmentVariables>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Pass Environment Variables to Build Tasks

Source: https://github.com/eirslett/frontend-maven-plugin/wiki/Home

Demonstrates how to inject custom environment variables into build tasks like gulp, grunt, or karma. These variables become accessible within the Node.js process via process.env.

```xml
<configuration>
    <environmentVariables>
        <OUTPUT_DIR>${project.build.directory}</OUTPUT_DIR>
    </environmentVariables> 
</configuration>
```

--------------------------------

### Configure Karma Test Runner

Source: https://context7.com/eirslett/frontend-maven-plugin/llms.txt

This snippet shows how to integrate Karma unit tests into the Maven test lifecycle. It specifies a custom path for the Karma configuration file.

```xml
<plugin>
    <groupId>com.github.eirslett</groupId>
    <artifactId>frontend-maven-plugin</artifactId>
    <version>2.0.0</version>
    <executions>
        <execution>
            <id>install node and npm</id>
            <goals>
                <goal>install-node-and-npm</goal>
            </goals>
            <configuration>
                <nodeVersion>v24.12.0</nodeVersion>
            </configuration>
        </execution>
        <execution>
            <id>npm install</id>
            <goals>
                <goal>npm</goal>
            </goals>
        </execution>
        <execution>
            <id>javascript tests</id>
            <goals>
                <goal>karma</goal>
            </goals>
            <phase>test</phase>
            <configuration>
                <karmaConfPath>src/test/javascript/karma.conf.ci.js</karmaConfPath>
            </configuration>
        </execution>
    </executions>
</plugin>
```

--------------------------------

### Configure Yarn with Private Registry

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Commands to set a private registry for Yarn to ensure yarn.lock references internal modules, and the corresponding Maven plugin configuration.

```bash
yarn config set registry <your_registry_url>
yarn install
```

```xml
<execution>
    <id>yarn install</id>
    <goals>
        <goal>yarn</goal>
    </goals>
    <configuration>
        <arguments>install</arguments>
        <npmRegistryURL>http://myregistry.example.org/</npmRegistryURL>
    </configuration>
</execution>
```

--------------------------------

### Importing Dependencies and Modules in JavaScript

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/frontend-maven-plugin/src/it/example project/index.html

This snippet shows how to import the jQuery library and a custom local module. It then uses the imported square function to update the text content of the document body.

```javascript
import $ from "jquery";
import { square } from "./src/main/javascript/square.js";

$(document.body).text(square(5));
```

--------------------------------

### Disable Proxy Inheritance for Package Managers

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configures the plugin to prevent npm, bower, or yarn from inheriting proxy settings from the Maven configuration. This is useful when specific tools cannot access resources through the configured proxy.

```xml
<configuration>
    <npmInheritsProxyConfigFromMaven>false</npmInheritsProxyConfigFromMaven>
</configuration>
```

```xml
<configuration>
    <bowerInheritsProxyConfigFromMaven>false</bowerInheritsProxyConfigFromMaven>
</configuration>
```

```xml
<execution>
    <id>tests</id>
    <goals>
        <goal>yarn</goal>
    </goals>
    <phase>compile</phase>
    <configuration>
        <yarnInheritsProxyConfigFromMaven>false</yarnInheritsProxyConfigFromMaven>
        <arguments>run test</arguments>
    </configuration>
</execution>
```

--------------------------------

### Ignore Test Failures

Source: https://github.com/eirslett/frontend-maven-plugin/blob/master/README.md

Configures a specific execution to ignore test failures, allowing the Maven build to continue even if the frontend tests fail.

```xml
<configuration>
    <testFailureIgnore>true</testFailureIgnore>
</configuration>
```