# Would like to have an example of a compiled plugin

**URL:** <https://discourse.joplinapp.org/t/would-like-to-have-an-example-of-a-compiled-plugin/12002>\
**Category:** Plugins\
**Created:** [27 October 2020 07:52 UTC](https://discourse.joplinapp.org/t/would-like-to-have-an-example-of-a-compiled-plugin/12002 "2020-10-27T07:52:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cph5489](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/cph5489/32/9977_2.png) [@cph5489](https://discourse.joplinapp.org/u/cph5489)\
**Post date:** [27 October 2020 07:52 UTC](https://discourse.joplinapp.org/t/would-like-to-have-an-example-of-a-compiled-plugin/12002/1 "2020-10-27T07:52:42Z")

</div>

I followed the steps on [Getting started with plugin development | Joplin (joplinapp.org)](https://joplinapp.org/api/get_started/plugins/)

First, npm gave a lot of notsup and optional warnings. But nevermind those as they are warnings not errors.

Then, I was able to "build" the plugin with the `npm run dist`, but now what? Should I be expecting a compiled file in dist? Or should I see anything, somewhere?  
The documentation does not say what I should expect.  
The npm tool said that it is built, should I trust it?

Finally, what path should I put in the plugin path field in Joplin?  
The document gave an example of `/home/user/src/joplin-plugin`, which is nice, until you find that there's also a `/src` folder under your project folder.  
Where should I point to?

Anyway, I followed the steps, dev console shows starting plugin, finished running, but NO console info.

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [27 October 2020 11:18 UTC](https://discourse.joplinapp.org/t/would-like-to-have-an-example-of-a-compiled-plugin/12002/2 "2020-10-27T11:18:11Z")

</div>

> [@cph5489](#):
>
> Then, I was able to "build" the plugin with the `npm run dist` , but now what? Should I be expecting a compiled file in dist? Or should I see anything, somewhere?

So is there a "dist" folder or not? There should be.

> [@cph5489](#):
>
> The document gave an example of `/home/user/src/joplin-plugin` , which is nice, until you find that there's also a `/src` folder under your project folder.

Why not try? Should be `/home/user/src/joplin-plugin` as the documentation says. The app will know where to look from there.

---

<div class="post-metadata">

**Author:** ![cph5489](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/cph5489/32/9977_2.png) [@cph5489](https://discourse.joplinapp.org/u/cph5489)\
**Post date:** [27 October 2020 11:48 UTC](https://discourse.joplinapp.org/t/would-like-to-have-an-example-of-a-compiled-plugin/12002/3 "2020-10-27T11:48:52Z")

</div>

Thanks for the reply.

There is a dist folder containing index.js, index.ts, and manifest.json

I tried a couple of paths, neither of them worked.  
I now put them under user/username\>/.config/joplin-desktop/plugins/test2  
Did not put anything in the options page plugin path box, as having both the path above and putting it in the path box will result in an error saying the plugin is already registered.

Still shows nothing in the console, though.  
Should have nothing to do with me using a Windows machine right?

---

<div class="post-metadata">

**Author:** ![tessus](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/tessus/32/13_2.png) [@tessus](https://discourse.joplinapp.org/u/tessus)\
**Post date:** [27 October 2020 14:47 UTC](https://discourse.joplinapp.org/t/would-like-to-have-an-example-of-a-compiled-plugin/12002/4 "2020-10-27T14:47:48Z")

</div>

The plugins category is to have a list of plugins. Development questions go to #development:plugins and support questions to #support.