Include astro-integration keyword in integrations catalogue
#1285
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
✅ Deploy Preview for astro-www-2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
HiDeoo
approved these changes
Oct 8, 2024
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.
We require the
astro-integrationkeyword to make an npm package work withastro add(docs), but never actually tracked that in the integrations catalogue, requiring one ofwithastroorastro-componentinstead. This PR updates the integrations script to also treatastro-integrationas a sufficient keyword to include a package in our catalogue and runs the update script to add a bunch of missing integrations.Most notably this includes Expressive Code!