Refactor: move prism to @astrojs/prism/components

[bholmesdev]

Changes

• Adds the <Prism/> component as default export from @astrojs/prism/component
• Removes the <Prism/> component from astro/components

☝️ Open to avoiding removal if we prefer. I think adding this component to @astrojs/prism could aid in the 1.0 beta move though.

Testing

N/A

Docs

withastro/docs#256

[changeset-bot]

🦋 Changeset detected

Latest commit: 9fa7127

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
astro	Patch
@astrojs/prism	Patch
@astrojs/markdown-remark	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[matthewp]

Added some comments

[matthewp]

Nit, but just @astrojs/prism/component with no (s)? There's not going to be multiple of these are there?

[bholmesdev]

I guess not! I really wanted to export from index.mjs but I can't figure out putting .astro files and ESM exports in the same file... Let me know if this is possible (without building the .astro file to JS of course)

[bholmesdev]

Update: changed to a default export:

import Prism from '@astrojs/prism/component';

[matthewp]

Yeah i was thinking that from the main would be nice but can't really do that, too bad. This works fine though, thanks!

[FredKSchott]

This is more than enough for now, but whenever we go to expose this to users I think the /component entrypoint API is a bit unexpected. I'd expect import {Prism} from '@astro/prism' to work.

I know this package is already doing double-duty, But, if the addAstro export will always be the "only used internally" export and Prism is the publicly available one, then I think a switch of the two would make sense when we go to expose this for users.

import {Prism} from '@astrojs/prism';
// in Astro: import {addAstro} from '@astrojs/prism/internal';