buildtools: add validator to check plugins are using standard build tools #510
Conversation
This file contains hidden or 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
s4kh
reviewed
Feb 11, 2026
| return | ||
| } | ||
|
|
||
| if !strings.Contains(string(b), "@grafana/create-plugin") { |
Contributor
There was a problem hiding this comment.
The author can bypass by creating custom webpack.config.ts and insert @grafana/create-plugin comment, right? But for now this is probably the best way to test it? Would there be any other checks we can do in the module.js file?
s4kh
approved these changes
Feb 11, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
New buildtools analyzer that detects plugins not built with Grafana's standard create-plugin tooling. It checks the source code for two things: