For more information visit Vento.
webstorm-vento is the plugin which integrates the Vento Template Engine with JetBrain's
IntelliJ Ultimate and WebStorm IDEs.
Take a look at the following screenshots to get a better idea of what the plugin can already do. The rest of the features are still under development. (see: backlog)
Important
- This plugin is in the early stages of development.
- The plugin is not yet available on the JetBrains Marketplace, but you can use the provided GitHub releases or build it yourself. (see: Installation below)
- Using the plugin depends on the presence of the Jetbrains JavaScript & TypeScript plug-in in your IDE. It is available by default in Webstorm (including with the free none-commercial license) but not in the community edition of IntelliJ IDEA.
Important
- You can use IntelliJ Community or Ultimate edition for development.
- Installing the built plugin in Webstorm works.
- The plugin is tested with Webstorm 2025.x.x and IntelliJ IDEA Ultimate 2025.x.x.
- Using JetBrains Marketplace (Not yet available):
- In the IDE go to Settings/Preferences > Plugins > Marketplace > Search for "WebStorm-Vento" > Install
- On the Go to JetBrains Marketplace search for "WebStorm-Vento", then download and install it.
Warning
NOT YET RELEASED TO MARKETPLACE
- Installing from a download:
- Download from GitHub Releases, or from the Marketplace, or build it yourself.
- In your IDE go to Settings/Preferences > Plugins > ⚙️ > Install plugin from disk...
Most of the following dependencies are provided automatically when Gradle is used to build the plugin.
- Vento
>= v2 - Deno
>= v2.3 - IntelliJ IDEA Community or Ultimate (for now only tested with
2025.2.*) - JDK
v21 - Gradle
v8.12 - Jetbrains JavaScript & TypeScript plug-in
v251.27812.49
- install ktlint and the prePushHook to make sure your code is formatted correctly.
- Clone the repository
- Run
./gradlew buildPlugin - The plugin will be built in
build/distributions - Install the plugin archive found in the
build/distributionsdirectory
./gradlew test./gradlew verifyPlugin./gradlew clean buildPLugin --no-build-cache --no-configuration-cacheTip
The Jetbrains SDK depends on a lot of magical dependencies to be able to run its own IDE's in development mode. So
sometimes there is no choice but to use the nuclear option to get a clean slate. This is likely to happen if you start
switching the platform being targeted by the plugin in gradle.properties or if you change the version of the
Jetbrains
SDK in build.gradle.kts.
./gradlew --stop ## stop the gradle daemon
rm -rf ~/.gradle/caches/ ## delete all caches






