Closed nabladev closed 6 years ago
The way plugin development is done changed recently in master, and the template hasn't yet been updated to accommodate.
If you're on a the latest Kibana master, you'll need to put your plugin in a kibana-extra
path, which lives next to kibana
.
.
├── kibana
└── kibana-extra
└── your-plugin
You'll then need to upgrade the version of @elastic/kibana-plugin-helpers
you are using. You'll probably also need to change the eslint setup, and link to the version in kibana
instead, and use the kbn
tool to install everything. Your plugin's package.json will include:
"@elastic/eslint-config-kibana": "link:../../kibana/packages/eslint-config-kibana",
"@elastic/eslint-import-resolver-kibana": "2.0.0",
"@elastic/plugin-helpers": "^9.0.2",
Then use kbn bootstrap
to install and link all the dependencies. Check out the contributing docs for information on setting things up.
I'll leave this open though, as a reminder to upgrade the template.
Closing this issue since the generator was forked into the Kibana repo, and works with the new dev setup. See https://github.com/elastic/kibana/tree/master/packages/kbn-plugin-generator.
Env:
My kibana and plugin directories are siblings.
$ ls: kibana/ stabHavana/
Kibana and ES run correctly. I only have this problem when I try to run Kibana with my plugin included. Kibana is forked for the repository so I'm currently working with the latest relase (7.0.0-alpha1). My plugin was generated runningsao kibana plugin
without any params and I generated everything except for hack and transation files.Hope this is useful!