Repository navigation
chore: add catalogue metadata to package.json - #16
Merged
Merged
Conversation
Adds the fields required for listing on nuxt.com/modules and for npm's discovery / README rendering: - keywords (including nuxt3 and nuxt4 — both work) - homepage (docs site) - bugs (issues URL) - author - engines (Node 18+) Matches the conventions used by other modules in the nuxt-modules org (e.g. sitemap, color-mode) and the nuxt/starter module template.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds the package.json fields required for listing on nuxt.com/modules and for npm's search/discovery UI. Zero behaviour change.
What's added
Why now
Step 1 of getting the module listed in the nuxt.com catalogue. Step 2 is a separate PR to nuxt/modules once v0.2.5 is on npm with this metadata — the catalogue's sync script auto-reads `keywords` / `description` / `homepage` from the live package, so they need to be published first.
Step 3 (much later) is opening an adoption issue at nuxt/modules to join the `nuxt-modules` org once the module's been listed and maintained for a release or two.
Test plan