Skip to main content
Version: 2.45.0

Platformatic Vite

The Platformatic Vite allows to run a Vite application as a Platformatic Runtime service with no modifications.

Getting Started​

Create or copy a Vite application inside the web or services folder. If you are not using autoload, you also have to explictly add the new service.

You are all set, you can now start your runtime as usual via wattpm dev or plt start.

Example configuration file​

{
  "$schema": "https://schemas.platformatic.dev/@platformatic/vite/2.0.0.json",
  "application": {
    "basePath": "/frontend"
  }
}

Architecture​

When running in development mode, the Vite development server is run a in worker thread in the same process of the Platformatic runtime. The server port is chosen randomly and it will override any user setting.

When running in production mode, a custom Fastify server will serve the built application. The service is run a in worker thread in the same process of the Platformatic runtime and it will not start a TCP server unless it's the runtime entrypoint.

In both modes if the service uses the commands property then it's responsible to start a HTTP server. The Platformatic runtime will modify the server port replacing it with a random port and then it will integrate the external service in the runtime.

If the application is a SSR application, it is only supported if using @fastify/vite.

Using custom commands and @fastify/vite​

Due to CVE-2025-24010, you need to set:

{
  ...
  "server": {
    "allowedHosts": [".plt.local"]
  }
}

This will allow other services inside the platformatic mesh network to contact your Vite server.

Configuration​

See the configuration page.

API​

  • platformatic.setBasePath(path): This function can be use to override the base path for the service. If not properly configure in the composer, this can make your application unaccessible.
  • platformatic.serviceId: The id of the service.
  • platformatic.workerId: The id of the service worker.
  • platformatic.root: The root directory of the service.
  • platformatic.basePath: The base path of the service in the composer.
  • platformatic.logLevel: The log level configured for the service.

Issues​

If you run into a bug or have a suggestion for improvement, please raise an issue on GitHub or join our Discord feedback channel.