WebStorm Plugin Development
Plugins: JetBrains Marketplace
WebStorm is an IntelliJ Platform-based product. Plugin projects for WebStorm can be developed using IntelliJ IDEA.
tip
WebStorm is free for non-commercial use
note
Follow Building a Plugin for WebStorm – Tutorial for JavaScript Developers blog post series to get started and How To Build a Plugin for JetBrains IDEs (Analog.js Example) webinar.
Define a dependency using webstorm(), see Versions link on top of this page for all available versions. See Local IntelliJ Platform IDE Instance for using a local installation.
A dependency on the bundled JavaScript plugin must be added using the bundledPlugin() helper.
Minimum build.gradle.kts setup:
repositories {
mavenCentral()
intellijPlatform {
defaultRepositories()
}
}
dependencies {
intellijPlatform {
webstorm("<versionNumber>")
bundledPlugin("JavaScript")
}
}The configuration of WebStorm plugin projects follows the methods described in Configuring Plugin Projects using the IntelliJ IDEA Product Attribute and Configuring the plugin.xml File for PhpStorm.
The table below summarizes the Gradle IntelliJ Plugin (1.x) attributes to set in the plugin project's Gradle build script. Click on an entry in the table's Attribute column to go to the documentation about that attribute. To see how these attributes appear in a similar Gradle build script for PhpStorm, see Configuring Gradle Build Script Using the IntelliJ IDEA Product Attribute.
| Attribute Value |
|---|---|
| |
| |
Dependency on the | |
Path to locally installed target version of WebStorm. For example, for macOS: |
The dependency on the WebStorm APIs must be declared in the plugin.xml file. As described in Modules Specific to Functionality table, the <depends> tags must declare JavaScript.
Note that for WebStorm, the plugin.xml file must also declare a dependency on com.intellij.modules.platform because JavaScript is not recognized as a module. Otherwise, the plugin is assumed to be a legacy plugin and will not load in WebStorm.
note
See WebStorm Extension Point and Listener List for the complete list.
See Exploring APIs as a Consumer. Test your plugin with any version of WebStorm you wish to support.
To use existing test base classes, add TestFrameworkType.Plugin.JavaScript test-framework available from Plugin Test Frameworks.
Alternatively, specify com.jetbrains.intellij.javascript:javascript-test-framework:$VERSION$ as testImplementation dependency explicitly (see IntelliJ Platform Artifacts Repositories).
When learning new plugin development, it is helpful to have some representative projects for reference: