# Kibana compatible plugins for 5.5.1
**URL:** https://discuss.elastic.co/t/kibana-compatible-plugins-for-5-5-1/92731
**Category:** Kibana
**Created:** [July 11, 2017, 11:11pm UTC](https://discuss.elastic.co/t/kibana-compatible-plugins-for-5-5-1/92731 "2017-07-11T23:11:16Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@bishwajeet](https://discuss.elastic.co/u/bishwajeet)
#### Post date: [July 11, 2017, 11:11pm UTC](https://discuss.elastic.co/t/kibana-compatible-plugins-for-5-5-1/92731/1 "2017-07-11T23:11:16Z")
I am trying to develop a custom plugin for kibana 5.5.1. Where can I find examples of such plugins ? I tried looking at [https://www.elastic.co/guide/en/kibana/current/known-plugins.html#\_timelion\_extensions](https://www.elastic.co/guide/en/kibana/current/known-plugins.html#_timelion_extensions) . However, none of them seems to work for 5.5.1 . I tried changing the kibana version in package.json . However, it seems the optimization fails for almost all of them. You need to do more than bump versions.
./kibana-plugin install
probably would need to be updated for every little major/minor version. There's all kinds of advice but they are old/invalid. I already see 6.0.0 beta coming up. Can you guys please post a decent tutorial for custom kibana plugin development ?
Thanks
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [July 12, 2017, 1:40am UTC](https://discuss.elastic.co/t/kibana-compatible-plugins-for-5-5-1/92731/2 "2017-07-12T01:40:34Z")
It's likely related to [Fatal Error after upgrading from 5.4.2 to 5.5.0](https://discuss.elastic.co/t/fatal-error-after-upgrading-from-5-4-2-to-5-5-0/92351/11)
---
### Author:  [@bishwajeet](https://discuss.elastic.co/u/bishwajeet)
#### Post date: [July 17, 2017, 4:37pm UTC](https://discuss.elastic.co/t/kibana-compatible-plugins-for-5-5-1/92731/3 "2017-07-17T16:37:37Z")
Hi @warkolm, It is not related. I do not have a old plugin. This is a fresh installation from the branch tagged v5.5.0 at [https://github.com/elastic/kibana](https://github.com/elastic/kibana)
Here is my directory structure:
```
plugins/
└── kb_newplugin
├── README.md
├── TRANSLATION.md
├── gather-info.js
├── index.js
├── node_modules
├── npm-debug.log
├── package.json
└── public
```
Inside index.js, to register the plugin, I need to give the full path like -
`visTypes: ['plugins/kb_newplugin/public/kb_newplugin.js'] .`
I went through the examples, they don't need to give the full path. Anything which you see wrong in the directory structure ?
---
### Author:  [@bishwajeet](https://discuss.elastic.co/u/bishwajeet)
#### Post date: [July 24, 2017, 9:58pm UTC](https://discuss.elastic.co/t/kibana-compatible-plugins-for-5-5-1/92731/4 "2017-07-24T21:58:25Z")
I finally found out why it was happening.
KIbana's sao template plugin generates a index.js and package.json after replacing underscores with dashes. So, your plugin directory name may contain underscores, but your plugin name is incorrect in both index.js and package.json. You need to manually fix that before proceeding.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 21, 2017, 9:58pm UTC](https://discuss.elastic.co/t/kibana-compatible-plugins-for-5-5-1/92731/5 "2017-08-21T21:58:41Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.