mirror of
https://github.com/supabase/supabase.git
synced 2026-10-18 23:59:08 +03:00
Migrates client SDK References to App Router. (Management and CLI API references aren't migrated yet, nor are self-hosting config references.) Some notes: Big changes to the way crawler pages are built and individual section URLs (e.g., javascript/select) are served. All of these used to be SSG-generated pages, but the number of heavy pages was just too much to handle -- slow as molasses and my laptop sounded like it was taking off, and CI sometimes refuses to build it all at all. Tried various tricks with caching and pre-generating data but no dice. So I changed to only building one copy of each SDK+version page, then serving the sub-URLs through a response rewrite. That's for the actual user-visible pages. For the bot pages, each sub-URL needs to be its own page, but prebuilding it doesn't work, and rendering on demand from React components is too slow (looking for super-fast response here for SEO). Instead I changed to using an API route that serves very minimal, hand-crafted HTML. It looks ugly, but it's purely for the search bots. You can test what bots see by running curl --user-agent "Mozilla/5.0 (iPhone; CPU iPhone OS 6_0 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A5376e Safari/8536.25 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" <URL_OF_PAGE> Also added some smoke tests to run against prod for the crawler routes, since we don't keep an eye on those regularly, and Vercel config changes could surprise-break them. Tested the meta images on Open Graph and all seems to work fine. With this approach, full production builds are really fast: ~5 minutes Starts using the new type spec handling, which is better at finding params automatically, so I could remove some of the manually written ones from the spec files.
50 lines
1.6 KiB
TypeScript
50 lines
1.6 KiB
TypeScript
import matter from 'gray-matter'
|
|
import { readFile } from 'node:fs/promises'
|
|
import { join } from 'node:path'
|
|
|
|
import { MDXRemoteBase } from '~/features/docs/MdxBase'
|
|
import { components } from '~/features/docs/MdxBase.shared'
|
|
import { RefSubLayout } from '~/features/docs/Reference.ui'
|
|
import { cache_fullProcess_withDevCacheBust } from '~/features/helpers.fs'
|
|
import { REF_DOCS_DIRECTORY } from '~/lib/docs'
|
|
|
|
async function getRefMarkdownInternal(relPath: string) {
|
|
const fullPath = join(REF_DOCS_DIRECTORY, relPath + '.mdx')
|
|
|
|
try {
|
|
if (!fullPath.startsWith(REF_DOCS_DIRECTORY)) {
|
|
throw Error(`Accessing forbidden path outside of REF_DOCS_DIRECTORY: ${fullPath}`)
|
|
}
|
|
|
|
const mdx = await readFile(fullPath, 'utf-8')
|
|
const { content } = matter(mdx)
|
|
return content
|
|
} catch (err) {
|
|
console.error(`Error fetching reference markdown from file: ${fullPath}:\n\n${err}`)
|
|
return ''
|
|
}
|
|
}
|
|
|
|
/**
|
|
* Caching this for the entire process is fine because the Markdown content is
|
|
* baked into each deployment and cannot change. There's also nothing sensitive
|
|
* here: this is just reading the public MDX files from the codebase.
|
|
*/
|
|
const getRefMarkdown = cache_fullProcess_withDevCacheBust(
|
|
getRefMarkdownInternal,
|
|
REF_DOCS_DIRECTORY,
|
|
(filename: string) => JSON.stringify([filename.replace(/\.mdx$/, '')])
|
|
)
|
|
|
|
interface MDXRemoteRefsProps {
|
|
source: string
|
|
}
|
|
|
|
function MDXRemoteRefs({ source }: MDXRemoteRefsProps) {
|
|
const refComponents = { ...components, RefSubLayout }
|
|
|
|
return <MDXRemoteBase source={source} components={refComponents} />
|
|
}
|
|
|
|
export { getRefMarkdown, MDXRemoteRefs }
|