diff --git a/src/content/docs/en/reference/publish-to-npm.mdx b/src/content/docs/en/reference/publish-to-npm.mdx index 4b46c62cc497c..73c7c48288513 100644 --- a/src/content/docs/en/reference/publish-to-npm.mdx +++ b/src/content/docs/en/reference/publish-to-npm.mdx @@ -1,6 +1,6 @@ --- -title: Publish to NPM -description: Learn how to publish Astro components to NPM +title: Publish to npm +description: Learn how to publish Astro components to npm i18nReady: true --- import { Steps } from '@astrojs/starlight/components'; @@ -8,7 +8,7 @@ import { FileTree } from '@astrojs/starlight/components'; Building a new Astro component? **Publish it to [npm!](https://npmjs.com/)** -Publishing an Astro component is a great way to reuse your existing work across your projects, and to share with the wider Astro community at large. Astro components can be published directly to and installed from NPM, just like any other JavaScript package. +Publishing an Astro component is a great way to reuse your existing work across your projects, and to share with the wider Astro community at large. Astro components can be published directly to and installed from npm, just like any other JavaScript package. Looking for inspiration? Check out some of our favorite [themes](https://astro.build/themes/) and [components](https://astro.build/integrations/) from the Astro community. You can also [search npm](https://www.npmjs.com/search?q=keywords:astro-component,withastro) to see the entire public catalog. @@ -171,7 +171,7 @@ Add `astro-component` or `withastro` as a special keyword to maximize its discov ``` :::tip -Keywords are also used by our [integrations library](https://astro.build/integrations/)! [See below](#integrations-library) for a full list of keywords we look for in NPM. +Keywords are also used by our [integrations library](https://astro.build/integrations/)! [See below](#integrations-library) for a full list of keywords we look for in npm. ::: --- @@ -269,14 +269,14 @@ Do you need some help building your integration, or just want to meet other inte ### `package.json` data -The library is automatically updated weekly, pulling in every package published to NPM with the `astro-component` or `withastro` keyword. +The library is automatically updated weekly, pulling in every package published to npm with the `astro-component` or `withastro` keyword. The integrations library reads the `name`, `description`, `repository`, and `homepage` data from your `package.json`. Avatars are a great way to highlight your brand in the library! Once your package is published you can [file a GitHub issue](https://github.com/withastro/astro.build/issues/new/choose) with your avatar attached and we will add it to your listing. :::tip -Need to override the information our library reads from NPM? No problem! [File an issue](https://github.com/withastro/astro.build/issues/new/choose) with the updated information and we'll make sure the custom `name`, `description`, or `homepage` is used instead. +Need to override the information our library reads from npm? No problem! [File an issue](https://github.com/withastro/astro.build/issues/new/choose) with the updated information and we'll make sure the custom `name`, `description`, or `homepage` is used instead. ::: ### Categories