1
0
mirror of https://github.com/laurent22/joplin.git synced 2024-12-15 09:04:04 +02:00
joplin/packages/generator-joplin/generators/app/templates
2021-08-10 11:34:49 +01:00
..
api Plugins: Updated types 2021-08-10 11:34:49 +01:00
src Setup version 2.2 2021-07-03 16:40:44 +01:00
.gitignore_TEMPLATE Generator: Update plugin generator to handle requirements of coming plugin repository 2021-01-04 18:45:43 +00:00
.npmignore_TEMPLATE Generator: Update plugin generator to handle requirements of coming plugin repository 2021-01-04 18:45:43 +00:00
api_index.ts Plugins: Added support app_min_version property and made it required 2020-11-15 14:18:46 +00:00
GENERATOR_DOC.md Doc: Updated doc and tests for plugin postMessage() update 2021-01-11 23:34:06 +00:00
package_TEMPLATE.json Generator: Fixed issue that could result in an invalid JPL file 2021-01-13 12:16:36 +00:00
plugin.config.json Generator: Better handling of external scripts 2021-01-08 16:31:11 +00:00
README.md Generator: Added "npm run update" command 2021-01-05 21:59:16 +00:00
tsconfig.json Plugins: Added support app_min_version property and made it required 2020-11-15 14:18:46 +00:00
webpack.config.js Generator: Include JSON files in webpack config 2021-06-12 00:18:33 +02:00

Joplin Plugin

This is a template to create a new Joplin plugin.

The main two files you will want to look at are:

  • /src/index.ts, which contains the entry point for the plugin source code.
  • /src/manifest.json, which is the plugin manifest. It contains information such as the plugin a name, version, etc.

Building the plugin

The plugin is built using Webpack, which creates the compiled code in /dist. A JPL archive will also be created at the root, which can use to distribute the plugin.

To build the plugin, simply run npm run dist.

The project is setup to use TypeScript, although you can change the configuration to use plain JavaScript.

Updating the plugin framework

To update the plugin framework, run npm run update.

In general this command tries to do the right thing - in particular it's going to merge the changes in package.json and .gitignore instead of overwriting. It will also leave "/src" as well as README.md untouched.

The file that may cause problem is "webpack.config.js" because it's going to be overwritten. For that reason, if you want to change it, consider creating a separate JavaScript file and include it in webpack.config.js. That way, when you update, you only have to restore the line that include your file.