Skip to content
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

[regression] Markdown component generates console error in 2.6 #7335

Closed
1 task
birtles opened this issue Jun 8, 2023 · 1 comment · Fixed by #7343
Closed
1 task

[regression] Markdown component generates console error in 2.6 #7335

birtles opened this issue Jun 8, 2023 · 1 comment · Fixed by #7343
Assignees
Labels
- P4: important Violate documented behavior or significantly impacts performance (priority)

Comments

@birtles
Copy link

birtles commented Jun 8, 2023

What version of astro are you using?

2.6.1

Are you using an SSR adapter? If so, which one?

No

What package manager are you using?

yarn

What operating system are you using?

Linux

What browser are you using?

Firefox

Describe the Bug

When using the <Markdown> component from @astrojs/markdown-component and running astro build now generates a console error:

The <Markdown> component is not available in SSR. See https://github.com/withastro/rfcs/discussions/179 for more info.

This is despite the fact that it is being used in SSG mode.

It didn't use to do with this before 2.6.

I'm guessing this is due to the redirects work in #7067 since that made us stop using onlyAvailableInSSR (which, it seems like we probably could have deleted at that point).

You can reproduce this in the linked-to StackBlitz container by running npx astro build from the command line.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-ch7wk5?file=src%2Fpages%2Findex.astro

Participation

  • I am willing to submit a pull request for this issue.
@matthewp matthewp self-assigned this Jun 8, 2023
@matthewp matthewp added the - P4: important Violate documented behavior or significantly impacts performance (priority) label Jun 8, 2023
@matthewp
Copy link
Contributor

matthewp commented Jun 9, 2023

Thanks, fix should be released today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- P4: important Violate documented behavior or significantly impacts performance (priority)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants