All Classes and Interfaces
Class
Description
A base class for commands providing helpers for common file generation
actions.
Abstract class for generating client files.
Exception indicating a failure during extraction of an archive file.
Handle extracting file archives.
Bundle handling methods.
Identifier for a chunk or part of the JS bundle.
Interface for annotated and subclass class searches.
Implementation that proxy and cache a real
ClassFinder.Implementation that searches for annotated classes or subclasses in a
list of classes.
Holds information about a class and its frontend dependencies.
A container for CssImport information when scanning the class path.
Utilities for commercial product handling.
Default implementation for file archive extraction.
Default file downloader implementation.
Exception indicating a failure during file download.
A factory for creating Vaadin Endpoint generator tasks.
A simple container with the information related to an application entry
point, i.e. those classes annotated with the
Route annotation,
extending WebComponentExporter and a bunch of more internal classes.The type of an entry point (scanned for frontend dependencies).
Excludes dependencies listed in an "exclusions" array of
vaadin-*versions.json file from a package.json.
Thrown by
FallibleCommand if it's unable to complete its execution.A generic command which may fail.
Handle file download from given url to target destination.
Utility class for frontend build operations.
Represents the class dependency tree of the application.
Frontend dependencies scanner.
Frontend dependencies scanner factory.
Provides access to frontend tools (Node.js and npm, pnpm, bun) and optionally
installs the tools if needed.
Helps to locate the tools in the system by their names.
Configuration object for controlling the
FrontendTools features.Generates embeddable web component files in npm mode, hiding the complexity
caused by using a different class loader.
A helper for tasks to handle generated files.
Collect generated-flow-imports content for project to use to determine if
dev-bundle contains all required imports.
Exception indicating a failure during installation of node and npm.
Shared code for managing contents of jar files.
Node installation class.
An executor that it's run when the servlet context is initialised in dev-mode
or when flow-maven-plugin goals are run.
Base abstract class for frontend updaters that needs to be run when in
dev-mode or from the flow maven plugin.
Build a
NodeExecutor instance.Helpers related to the production bundle.
Proxy configuration used for downloads and executions.
Class for holding proxy information.
Factory for reading proxy configurations from various sources including
system properties, .npmrc files, and environment variables.
Clean any frontend files generated for creation on a new development or
production bundle.
Copies all frontend resources from JAR files into a given folder.
Copies JavaScript files from the given local frontend folder.
Copies JavaScript and CSS files from JAR files into a given folder.
Copies template files to the target folder so as to be available for parsing
at runtime in production mode.
A task for generating the bootstrap file
FrontendUtils.BOOTSTRAP_FILE_NAME during `package` Maven goal.Generate
commercial-banner.js if it is missing in
frontend/generated folder.Generate the TS files for endpoints, and the Client API file.
A task for generating the feature flags file
FrontendUtils.FEATURE_FLAGS_FILE_NAME during `package` Maven goal.Generate
index.html if it is missing in frontend folder.Generate
index.ts if it is missing in frontend folder.Generate OpenAPI json file for Vaadin Endpoints.
Creates the
package.json if missing.Generates necessary PWA icons.
Generate default files for react-router if missing from the frontend folder.
Generate
index.html if it is missing in frontend folder.Generate
tailwind.css if it is missing in the generated frontend
folder.Generate
tailwind.js wrapper if it is missing in the generated
frontend folder.Generate
tsconfig.json if it is missing in project folder.Generate
types.d.ts if it is missing in project folder and
tsconfig.json exists in project folder.Generate
vite-devmode.ts if it is missing in frontend/generated
folder.A task for generating the bootstrap file for exported web components
FrontendUtils.WEB_COMPONENT_BOOTSTRAP_FILE_NAME during `package`
Maven goal.Generate
web-component.html if it is missing in frontend folder.Task that installs any Flow frontend plugins into node_modules/@vaadin for
use with frontend compilation.
Copies production bundle files from pre-compiled bundle JAR into a folder
where production bundle is normally located.
Process CSS files in META-INF/resources for production build.
Deletes old files from frontend generated folder.
Compiles the dev mode bundle if it is out of date.
Run
npm install after dependencies have been updated.An updater that it's run when the servlet context is initialised in dev-mode
or when flow-maven-plugin goals are run in order to update Flow imports file
and "jar-resources" contents by visiting all
classes with
JsModule and Theme annotations.Updated
index.ts if it imports Flow from an old location.Updates
package.json by visiting NpmPackage annotations
found in the classpath.Creates a vaadin-dev-server-settings.json file for use with dev server
configuration.
Task generating the theme definition file 'theme.js' for importing
application theme into the generated frontend directory.
Updates the Vite configuration files according with current project settings.
Theme handling methods.
Implemented by classes that want to modify the bootstrap typescript.
Exception thrown for when a node task that is not in the task list is
encountered.
Exception indicating a failure during downloaded archive verification.