> Markdown version of [Configuration](https://vaadin.com/docs/v24/hilla/reference/configuration). Section index: [llms.txt](https://vaadin.com/docs/v24/hilla/llms.txt)

# Configuration

## <a id="java-compiler-options"></a>Configure the Endpoint Generator

To allow the [endpoint generator](https://vaadin.com/docs/v24/hilla/reference/endpoint-generator.md) to use the correct parameter names when building TypeScript files, you need to configure the Java compiler not to omit them by using the `javac -parameters` option. For example, the following shows how to configure the Maven plugin to include this compiler option:

`pom.xml`

```xml
<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <version>3.10.1</version>
            <configuration>
                <encoding>UTF-8</encoding>
                <parameters>true</parameters>
            </configuration>
        </plugin>
    </plugins>
</build>
```

## <a id="multi-module-projects-or-external-dependency-endpoints"></a>Multi-Module Projects or External Dependency Endpoints

By default, Hilla searches only for endpoints in your application. You can extend the search, though, to other modules in your project, or even to dependencies, like the [SSO Kit](https://vaadin.com/docs/v24/tools/sso.md).

The Hilla Maven plugin can be configured to list the Java packages that contain the endpoints. That list should always include the main application package and can include other packages as needed.

If your application is in a package named `com.example.application`, and you have another module containing endpoints in `com.example.module`, and you want to use some third-party endpoints in `com.acme.module`, you can configure the plugin as follows:

```xml
<plugin>
    <groupId>com.vaadin.hilla</groupId>
    <artifactId>hilla-maven-plugin</artifactId>
    <version>${hilla.version}</version>
    <!-- Add this configuration -->
    <configuration>
        <parser>
            <packages>
                <package>com.example.application</package>
                <package>com.example.module</package>
                <package>com.acme.module</package>
            </packages>
        </parser>
    </configuration>
    <!-- ... -->
</plugin>
```

> **Note: Endpoints & Spring Dependencies**
>
> If endpoints external to the main application have autowired Spring dependencies, make sure that Spring can find them. Otherwise, Hilla tries to instantiate them using a default no-arguments constructor, which won’t trigger dependency injection.

## <a id="ts-compiler-options"></a>TypeScript Compiler Options

The TypeScript compiler requires a `tsconfig.json` file. If there is no `tsconfig.json` in the project root, the `vaadin-maven-plugin` generates one.

The default configuration looks similar to the following:

`tsconfig.json`

```json
{
  "compilerOptions": {
    "sourceMap": true,
    "inlineSources": true,
    "module": "esNext",
    "target": "es2017",
    "moduleResolution": "node",
    "strict": true,
    "noFallthroughCasesInSwitch": true,
    "noImplicitReturns": true,
    "noImplicitAny": true,
    "noImplicitThis": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "experimentalDecorators": true,
    "baseUrl": "frontend",
    "paths": {
      "Frontend/*": [
        "*"
      ]
    }
  },
  "include": [
    "frontend/**/*.ts",
    "frontend/index.js",
    "types.d.ts"
  ],
  "exclude": []
}
```

## <a id="core-pro-vaadin-react-components"></a>Core & Pro Vaadin React Components

Vaadin React components include free core components and Pro (commercial) components. They’re shipped in separate npm packages: `@vaadin/react-components`, which contains only free components; and `@vaadin/react-components-pro`, which contains only commercial components. Vaadin adds both of these packages to `package.json` if the `com.vaadin:vaadin` artifact is used in the Java project configuration. By default, this is done in the Maven `pom.xml`.

pom.xml

```xml
<dependency>
	<groupId>com.vaadin</groupId>
	<artifactId>vaadin</artifactId>
</dependency>
```

If the `com.vaadin:vaadin-core` dependency is used, only the free `@vaadin/react-components` package is added:

pom.xml

```xml
<dependency>
	<groupId>com.vaadin</groupId>
	<artifactId>vaadin-core</artifactId>
</dependency>
```

## <a id="enable-react-19"></a>Enable React 19

Hilla uses by default React 18, but is tested against both React 18 and 19. Thus you can enable React 19 using feature flag.

Edit the `src/main/resources/vaadin-featureflags.properties` file in your application folder, to enable the feature flag.

`vaadin-featureflags.properties`

```properties
com.vaadin.experimental.react19=true
```