Updated the webpack configuration to analyze plugin code during builds and auto-generate a plugin.generated.json file which holds information about extensions the plugin wants to register. (This can later be used by Grafana core to decide when a certain plugin should be preloaded.)
What should I do as a plugin dev?
Run npx @grafana/create-plugin@latest update once this PR is merged and a new version of @grafana/create-plugin is published.
📦 Published PR as canary version: Canary Versions
:sparkles: Test out this PR locally via:
```bash
npm install @grafana/create-plugin@4.10.0-canary.871.60a4cf1.0
# or
yarn add @grafana/create-plugin@4.10.0-canary.871.60a4cf1.0
```
Hello! 👋 This repository uses Auto for releasing packages using PR labels.
✨ This PR can be merged and will trigger a new minor release.
NOTE: When merging a PR with the release label please avoid merging another PR. For further information see here.
What changed?
Updated the webpack configuration to analyze plugin code during builds and auto-generate a
plugin.generated.json
file which holds information about extensions the plugin wants to register. (This can later be used by Grafana core to decide when a certain plugin should be preloaded.)What should I do as a plugin dev?
Run
npx @grafana/create-plugin@latest update
once this PR is merged and a new version of@grafana/create-plugin
is published.📦 Published PR as canary version:
Canary Versions
:sparkles: Test out this PR locally via: ```bash npm install @grafana/create-plugin@4.10.0-canary.871.60a4cf1.0 # or yarn add @grafana/create-plugin@4.10.0-canary.871.60a4cf1.0 ```