From ba3ed9a32773857b98ab46ba49e962da1357dc2a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Leif=20=C3=85strand?= Date: Fri, 10 Apr 2026 08:31:55 +0300 Subject: [PATCH] Use the right frontend location for add-ons Same location as used in https://github.com/vaadin/client-server-addon-template --- articles/flow/component-internals/web-components/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/flow/component-internals/web-components/index.adoc b/articles/flow/component-internals/web-components/index.adoc index 6c55918c63..b8ceecdd6f 100644 --- a/articles/flow/component-internals/web-components/index.adoc +++ b/articles/flow/component-internals/web-components/index.adoc @@ -49,7 +49,7 @@ The `@Tag` annotation here defines the name of the HTML element. The `@JsModule` == Adding Frontend Files -Your component may require in-project frontend files, such as additional JavaScript modules. In which case, add them to the `src/main/resources/META-INF/frontend` directory so that they're packaged in the component JAR if you choose to make an add-on of your component. +Your component may require in-project frontend files, such as additional JavaScript modules. In which case, add them to the `src/main/resources/META-INF/resources/frontend` directory so that they're packaged in the component JAR if you choose to make an add-on of your component. As a example, you might use the `@JsModule` annotation to add a local JavaScript module like so: [source,java]