-
Notifications
You must be signed in to change notification settings - Fork 10.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
Naming conventions for plugins #4827
Comments
Sort of related to issue #4671 because as we expand what categories of plugins are included in the library, the naming conventions for plugins will likely need to change. |
We actually filter which NPM packages show up in the library using NPM "keywords" not the names of the packages so a package named The two keywords we match on (currently) are We specify these keywords in two places:
|
ok @KyleAMathews cool! Should I add those links to our Plugin Authoring doc? |
Perhaps not the links to the code as that's likely to change and not interesting to most people but definitely which keywords people should use. Add the two to the keywords bullet here We should perhaps have a section near the top making it very clear how they get their plugin to show up in the plugin library. |
Due to the high volume of issues, we're closing out older ones without recent activity. Please open a new issue if you need help! |
Description
Currently, the Plugin Authoring doc describes four categories in the Gatsby plugin/package naming convention. This covers most existing plugins. However, there is potential to add packages and plugins that must adhere to other naming conventions.
Problem
Here's an example scenario: if we add eslint to Gatsby and want to share it through the plugin library, we'll need to name it according to eslint.org's conventions:
eslint-plugin-<plugin-name>
. The plugin library would currently not pull this into search results, so we'd need to expand how the library finds packages and plugins.Additional Questions
@kkemple
The text was updated successfully, but these errors were encountered: