# Why my own plugin can't be packaged?

**URL:** <https://discuss.elastic.co/t/why-my-own-plugin-cant-be-packaged/178558>\
**Category:** Kibana\
**Created:** [April 26, 2019, 4:02am UTC](https://discuss.elastic.co/t/why-my-own-plugin-cant-be-packaged/178558 "2019-04-26T04:02:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yyl1988](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yyl1988/32/44681_2.png) [@yyl1988](https://discuss.elastic.co/u/yyl1988)\
**Post date:** [April 26, 2019, 4:02am UTC](https://discuss.elastic.co/t/why-my-own-plugin-cant-be-packaged/178558/1 "2019-04-26T04:02:52Z")

</div>

Hello, I'm developing on kibana6.4.3 source code version. When building the package (yarn build), why the plugins developed by myself can't be packaged?Thanks!

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [April 26, 2019, 4:34pm UTC](https://discuss.elastic.co/t/why-my-own-plugin-cant-be-packaged/178558/2 "2019-04-26T16:34:56Z")

</div>

Hey @yyl1988, are you running `yarn build` from within the folder of your custom plugin? If so, what is output in your terminal when doing so?

---

<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:** [May 24, 2019, 4:35pm UTC](https://discuss.elastic.co/t/why-my-own-plugin-cant-be-packaged/178558/3 "2019-05-24T16:35:03Z")

</div>

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