Joe Pea b960519608
feat: output type definitions, and allow new Docsify(opts) to accept options for ESM usage (#2392)
This `new Docsify(opts)` API can be safely converted to a Custom Element constructor with backwards compatibility later.
2025-12-03 21:49:44 -08:00

35 lines
856 B
HTML

<head>
<meta charset="utf-8" />
<meta
name="viewport"
content="width=device-width, initial-scale=1, viewport-fit=cover"
/>
<link rel="stylesheet" href="/node_modules/docsify/dist/themes/core.css" />
<style></style>
<script type="importmap">
{
"imports": {
"docsify": "/node_modules/docsify/src/core/Docsify.js",
"docsify/": "/node_modules/docsify/",
"prismjs": "/prism.js",
"prismjs/": "/node_modules/prismjs/",
"marked": "/node_modules/marked/lib/marked.esm.js",
"marked/": "/node_modules/marked/",
"tinydate": "/node_modules/tinydate/dist/tinydate.mjs",
"common-tags": "/node_modules/common-tags/es/index.js"
}
}
</script>
<script></script>
<script src="./example.js" type="module"></script>
</head>
<body>
<div id="app"></div>
</body>