-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This plugin is using link:
dependencies for non-Kibana packages
#40858
Comments
In the unpublished @kbn package I see this
Thus link dependency I got in the generated plugin doesn't really work, right? |
Here the packages.json of the plugin
|
Pinging @elastic/kibana-operations |
I found the same error. As a workaround while this is not fixed, you can create the plugin the way you did and then move it to the kibana-extra directory (that should be sibling to kibana directory). Also, replace the links in package.json, to point to kibana directory: ../../kibana |
I am having the same error message while installing my plugin to a Kibana instance. Is there any update? I am using Kibana version 7.3.0 . |
@elastic/kibana-platform this seems related to the plugin path changes. Could someone take a look? |
Having the same issue, Kibana 7.3.0 |
What worked for me was placing all kibana related dependencies to devDependencies. Hope this helps
|
The plugin I had to make changes to started working probably so this approach may help you as well. |
hello, |
i got the same issue, and the reason i found is the dependency of "@kbn/i18n": "link:../../packages/kbn-i18n" in package json file. i just move this dependency into dev dependencies, and it works, the translation works well too. |
I came across similar kind of issue. The way I solved is to use file: prefix instead of link: prefix. ie. "@kbn/i18n": "file:../../packages/kbn-i18n". yarn build created plugin zip with all such dependencies installed in node_modules of zip. I dont know if it is a standard way of doing it but it worked for me. |
* Fix paths for kibana packages in prepare_project_dependencies(#40858). * Dist/index.js after yarn build. * chore(NA): correctly include kbm pm new dist file * Commit after cherry-pick 985c85c from recreation branch. Co-authored-by: Tiago Costa <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
* Fix paths for kibana packages in prepare_project_dependencies(elastic#40858). * Dist/index.js after yarn build. * chore(NA): correctly include kbm pm new dist file * Commit after cherry-pick 985c85c from recreation branch. Co-authored-by: Tiago Costa <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
* Fix paths for kibana packages in prepare_project_dependencies(elastic#40858). * Dist/index.js after yarn build. * chore(NA): correctly include kbm pm new dist file * Commit after cherry-pick 985c85c from recreation branch. Co-authored-by: Tiago Costa <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
* Fix paths for kibana packages in prepare_project_dependencies(#40858). * Dist/index.js after yarn build. * chore(NA): correctly include kbm pm new dist file * Commit after cherry-pick 985c85c from recreation branch. Co-authored-by: Tiago Costa <[email protected]> Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Shailesh cheke <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
* Fix paths for kibana packages in prepare_project_dependencies(#40858). * Dist/index.js after yarn build. * chore(NA): correctly include kbm pm new dist file * Commit after cherry-pick 985c85c from recreation branch. Co-authored-by: Tiago Costa <[email protected]> Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Shailesh cheke <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
That was fixed with the merge of that PR #57097 for the mentioned version tags. |
@restrry yes, it should be solved with that PR and this one #57097 |
Kibana version:
7.2.0
Elasticsearch version:
7.2.0
Server OS version:
macOS v10.14.5 (Mojave)
Browser version:
Chrome Version 75.0.3770.100 (Official Build) (64-bit)
Browser OS version:
macOS v10.14.5 (Mojave)
Original install method (e.g. download page, yum, from source, etc.):
Download page, source (GitHub)
Describe the bug:
Unable to install a plugin generated by
kibana/scripts/generate_plugin
.Steps to reproduce:
Expected behavior:
I can install the generated plugin.
Plugin bootstrap:
The text was updated successfully, but these errors were encountered: