Partials are currently defined via MDX includes. This PR switches to pre-compile-time partials, which have a new syntax:
```
<$Partial path="path/to/file.mdx" />
```
## Rationale
This produces two improvements:
1. Partial substitution can occur in pipelines that don't use MDX compilation. For example, we can now do partial substitution before building the search index, so partial content will also be indexed.
2. After the App Router migration, the MDXProviders should've been deprecated, but were kept around for the sole reason of making partials work, and leading to us shipping unnecessary client-side code. We get a minor decrease in overall client bundle size (5.74 MB to 5.6 MB) by getting rid of the Providers.
## Breaking changes
Besides the change to partial syntax, the arguments are also less powerful than before because we are doing string substitution and don't have the full power of JS. Defining string variables is still possible (documented in the Contributing guide), and since that's all we actually do in practice, this shouldn't be too cumbersome. There is always the escape hatch of making a custom component for more complex content reuse cases.
* fix: consistent disk unit
* Update apps/docs/content/guides/platform/manage-your-usage/disk-throughput.mdx
* Update apps/docs/content/guides/platform/manage-your-usage/disk-throughput.mdx
* Update apps/docs/content/guides/platform/manage-your-usage/disk-throughput.mdx
* docs: makes use of singular/plural for metrics that are billed hourly consistent.
* ci: Autofix updates from GitHub workflow
* fix: instance is Mbps
* fix: description Mbps
---------
Co-authored-by: Thomas <31189692+ecktoteckto@users.noreply.github.com>
Co-authored-by: github-tidy-bot <github-tidy-bot@supabase.com>
* Bump vite to v6 to get the newest esbuild.
* Bump tsx to get the newest esbuild.
* Fix lodash version.
* Make the www app use the catalog version of next.
Webhooks are not firing locally unless we use `host.docker.internal` instead of `localhost`
Multiple people were encountering this issue, and it was discussed here:
https://github.com/supabase/supabase/issues/13005
Thanks!
* adds blog post and stub
* Adds dates
* adds a description
* reworking the blog
* blog og
* fix description
* updates
* adds the form
* change date
---------
Co-authored-by: Francesco Sansalvadore <f.sansalvadore@gmail.com>
* feat: add SOC 2 page to docs
* feat: more linking
* fix: make linters happy
* fix: prettier
* chore: make security page available
* typo: sp
* publish security
* chore: publish new security section
* change mobile menu to show Security on Security section
---------
Co-authored-by: Charis Lam <26616127+charislam@users.noreply.github.com>
Type docs pulled from JS client libraries were expected to be in version 0.22, which unfortunately is a bit old and incompatible with TypeScript 5. Therefore any JS lib that upgrades their toolchian to TS 5 will inadvertently break their type specs in docs.
This PR updates docs to also support 0.27 (the latest stable version, compatible with TS 5), in addition to the old version. Parallel support is required since many libs are still on the old version.
The main changes are:
- The comment shape has changed in typedoc.
- kindString has been deprecated in favor the kind numbers.
- indexSignatures are now plural (an array).
