next-mdx-remote
Version:
utilities for loading mdx from any remote source as data, rather than as a local import
62 lines (60 loc) • 2.17 kB
JavaScript
const mdx = require('@mdx-js/mdx')
const { MDXProvider, mdx: mdxReact } = require('@mdx-js/react')
const { transformAsync } = require('@babel/core')
const presetEnv = require('@babel/preset-env')
const presetReact = require('@babel/preset-react')
const pluginBrowser = require('./babel-plugin-mdx-browser')
const reactRenderToString = require('react-dom/server').renderToString
const React = require('react')
module.exports = function renderToString(
source,
{ components = {}, mdxOptions = {}, scope = {} } = {}
) {
let jsSource
// transform it into react
return mdx(source, { ...mdxOptions, skipExport: true })
.then((code) => {
// mdx gives us back es6 code, we then need to transform into two formats:
// - first a version we can render to string right now as a "serialized" result
// - next a version that is fully browser-compatible that we can eval to rehydrate
return Promise.all([
// this one is for immediate evaluation so we can renderToString below
transformAsync(code, {
presets: [presetReact, presetEnv],
configFile: false,
}),
// this one is for the browser to eval and rehydrate, later
transformAsync(code, {
presets: [presetReact, presetEnv],
plugins: [pluginBrowser],
configFile: false,
}),
])
})
.then(([now, later]) => {
// evaluate the code
// NOTES:
// - relative imports can't be expected to work with remote files, we'd need
// an extra babel transform to be able to import specific file paths
jsSource = later.code
return new Function(
'React',
'MDXProvider',
'mdx',
'components',
...Object.keys(scope),
`${now.code}
return React.createElement(MDXProvider, { components },
React.createElement(MDXContent, {})
);`
)(React, MDXProvider, mdxReact, components, ...Object.values(scope))
})
.then((component) => {
return {
compiledSource: jsSource,
// react: render to string
renderedOutput: reactRenderToString(component),
scope,
}
})
}