[CLI][codegen] Use yarn create @grafana/plugin to Generate Front-End Code
#491
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rd out when yarn command errors.
…22, and uses node 18, whereas ubuntu-24.04 uses node 20.
…generated plugin code.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of using a snapshot of the output of
yarn create @grafana/pluginwith some small tweaks when adding thefrontendcomponent withgrafana-app-sdk project component add, invoke theyarncommand directly, then tweak the output as needed. This keeps us from falling behind the current plugin bootstrapping. As yarn is required to build the frontend already, we have the component add check if yarn is installed, and error if not, requesting that the user must have yarn installed to add the frontend component.Resolves #473