Why
Content parsing reads the entire docs collection so that we can extract things such as permalinks
But it comes at cost - the full docs collection is being globed and ran through the markdown/rehype pipeline and it's taking about 5 seconds.
What
Disable it for now until we implement those features.
Later (new ticket or add to scope of link resolver tickets)
We likely want to keep import.meta.global as it provides out of the box (i.e., without having to write any more code):
- the populated
slug according to Astro's rules
permalinks field added by our remark plugin- cache invalidation
Until we find an alternative that performs well in the dev server we can turn this off permanently in dev mode, eventually exposing a flag in the configuration for users to enable it.
Other options considered
getCollection('docs')
This is not available on the collection code because the types for the function are generated by Astro on the application side.
Manual setup
we would have to find, read, build our own mdx enabled remark pipeline
Why
Content parsing reads the entire docs collection so that we can extract things such as permalinks
But it comes at cost - the full docs collection is being globed and ran through the markdown/rehype pipeline and it's taking about 5 seconds.
What
Disable it for now until we implement those features.
Later (new ticket or add to scope of link resolver tickets)
We likely want to keep
import.meta.globalas it provides out of the box (i.e., without having to write any more code):slugaccording to Astro's rulespermalinksfield added by our remark pluginUntil we find an alternative that performs well in the dev server we can turn this off permanently in dev mode, eventually exposing a flag in the configuration for users to enable it.
Other options considered
getCollection('docs')
This is not available on the collection code because the types for the function are generated by Astro on the application side.
Manual setup
we would have to find, read, build our own mdx enabled remark pipeline