Google Summer of Code 2020
Getting started with plugin development🔗
In this article you will learn the basic steps to build and test a plugin in Joplin.
Setting up your environment🔗
First you need to setup your environment:
You will also need to have Joplin installed and running in development mode, which we'll describe later.
But first install Yeoman and the Joplin Plugin Generator:
npm install -g yo generator-joplin
Then to create the plugin, run:
This will create the basic scafolding of the plugin. At the root of it, there is a number of configuration files which you normally won't need to change. Then the
src/ directory also contains a manifest.json file, which you can edit to set various information about the plugin, such as its name, homepage URL, etc.
Building the plugin🔗
src/index.ts already contain some basic code meant for testing the plugin. In particular it contains a call to joplin.plugins.register, which all plugins should call to register the plugin. And an
onStart() event handler, which will be executed by Joplin when the plugin starts.
To try this basic plugin, compile the app by running the following from the root of the project:
npm run dist
Doing so should compile all the files into the
dist/ directory. This is from here that Joplin will load the plugin.
Testing the plugin🔗
In order to test the plugin, you might want to run Joplin in Development Mode. Doing so means that Joplin will run using a different profile, so you can experiment with the plugin without risking to accidentally change or delete your data.
Finally, in order to test the plugin, open the Setting screen, then navigate the the Plugins section, and add the plugin path in the Development plugins text field. For example, if your plugin project path is
/home/user/src/joplin-plugin, add this in the text field.
Restart the app, and Joplin should load the plugin and execute its
onStart handler. If all went well you should see the test message in the plugin console: "Test plugin started!".