# Kibana custom plugins packaging

**URL:** <https://discuss.elastic.co/t/kibana-custom-plugins-packaging/274761>\
**Category:** Kibana\
**Tags:** kibana-plugin-development\
**Created:** [June 2, 2021, 1:52pm UTC](https://discuss.elastic.co/t/kibana-custom-plugins-packaging/274761 "2021-06-02T13:52:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pchakour](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@pchakour](https://discuss.elastic.co/u/pchakour)\
**Post date:** [June 2, 2021, 1:52pm UTC](https://discuss.elastic.co/t/kibana-custom-plugins-packaging/274761/1 "2021-06-02T13:52:03Z")

</div>

Hello 🙂

I have a question about plugins packaging, hope someone can help me.

I'm creating some custom plugins for Kibana and I want to create only one distribuable plugin to install all my plugins in once.

So, I setted up the following tree structure inspired by x-pack:

```
myPlugins/
 | .eslintrc.js
 | tsconfig.json
 | package.json
 | plugins/
   | plugin1/
     | common
     | server
     | public
     | translations
     | kibana.json
     | .i18nrc.json
   | plugin2/
      | ...

```

In development mode, all plugins are detected by Kibana based on the **kibana.json** file. But I don't known how to build the **myPlugins** directory to be distribuable. Unfortunately, the plugins helpers package not seems to be intended for this case.

Someone already did this kind of plugin ?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 30, 2021, 1:52pm UTC](https://discuss.elastic.co/t/kibana-custom-plugins-packaging/274761/2 "2021-06-30T13:52:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.