You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add script to identify plugin dependencies for TS project references migration (#80463)
* move kbn-dev-utils plugin helpers under a dedicated folder
* use getPluginSearchPaths in kbn-config & kbn-optimizer
* add a script to find plugin dependencies not migrated to TS project refs
* update docs
* add a script reporting all circular deps between plugins
based on kibana.json declaration, so it doesn't provide all the cases
* fix optimizer scan logic. removed by mistake
* revert changes. fails on CI
* remove prod depenedency on kbn/dev-utils
* remove last export
* only run plugin discovery once to speed up circular dep detection
* address comments
* address comments
* update fixtures
Co-authored-by: spalger <spalger@users.noreply.github.com>
Copy file name to clipboardExpand all lines: docs/developer/best-practices/typescript.asciidoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ This architecture imposes several limitations to which we must comply:
28
28
[discrete]
29
29
==== Prerequisites
30
30
Since project refs rely on generated `d.ts` files, the migration order does matter. You can migrate your plugin only when all the plugin dependencies already have migrated. It creates a situation where commonly used plugins (such as `data` or `kibana_react`) have to migrate first.
31
-
https://github.com/elastic/kibana/issues/79343 is going to provide a tool for identifying a plugin dependency tree.
31
+
Run `node scripts/find_plugins_without_ts_refs.js --id your_plugin_id` to get a list of plugins that should be switched to TS project refs to unblock your plugin migration.
0 commit comments