You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
When using Astro v3, Astro errors stating that it cannot render "Content" and states that "No valid renderer was found for this file extension." I believe it means that it cannot find any renderer for the .org (Orgmode) file extension however this integration is loaded (astro-org). This integration works perfectly when using Astro v2 and has for almost a year now. I spoke with someone on the Discord server in the dev channel and it was said that the move to Astro v3 shouldn't have caused any integrations to break, so I'm wondering if this might be an Astro issue or maybe there was a breaking change in the integration API that I haven't found documented yet?
What's the expected result?
I expect that this would successfully build a site using Orgmode files as source in place of markdown.
To see what I expect, you can change the astro version in the example to v2 and it will start working.
I haven't looked in-depth, but astro-org doesn't seem to be registering a renderer at all. It worked for astro 2.x by directly inserting vite plugins. Integration code. It also depends on jsxImportSource: 'astro', which no longer exists.
Astro Info
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
When using Astro v3, Astro errors stating that it cannot render "Content" and states that "No valid renderer was found for this file extension." I believe it means that it cannot find any renderer for the
.org
(Orgmode) file extension however this integration is loaded (astro-org). This integration works perfectly when using Astro v2 and has for almost a year now. I spoke with someone on the Discord server in the dev channel and it was said that the move to Astro v3 shouldn't have caused any integrations to break, so I'm wondering if this might be an Astro issue or maybe there was a breaking change in the integration API that I haven't found documented yet?What's the expected result?
I expect that this would successfully build a site using Orgmode files as source in place of markdown.
To see what I expect, you can change the astro version in the example to v2 and it will start working.
Link to Minimal Reproducible Example
https://stackblitz.com/edit/github-gzy1ea?file=package.json
Participation
The text was updated successfully, but these errors were encountered: