50e6f491ad
* Use npm package names to load internal deps This is necessary so that published Astro components work. These components will be built by esinstall and therefore they cannot rely on `_astro_internal`. The fix is to use npm specifiers everywhere. * Move most of frontend to internal * Mark astro/internal/markdown.js as external * Move markdown stuff to its own package This moves the markdown stuff to its own package so that we can externalize it in the markdown component. * Add the changeset
23 lines
599 B
JSON
23 lines
599 B
JSON
{
|
|
"name": "@astrojs/markdown-support",
|
|
"version": "0.1.0",
|
|
"main": "./dist/index.js",
|
|
"type": "commonjs",
|
|
"exports": {
|
|
".": "./dist/index.js"
|
|
},
|
|
"scripts": {
|
|
"prepublish": "yarn build",
|
|
"build": "astro-scripts build --format cjs \"src/**/*.ts\" && tsc -p tsconfig.json",
|
|
"dev": "astro-scripts dev \"src/**/*.ts\""
|
|
},
|
|
"devDependencies": {
|
|
"@types/github-slugger": "^1.3.0",
|
|
"github-slugger": "^1.3.0",
|
|
"rehype-parse": "^7.0.1",
|
|
"rehype-raw": "^5.1.0",
|
|
"rehype-stringify": "^8.0.0",
|
|
"unified": "^9.2.1",
|
|
"unist-util-visit": "^3.1.0"
|
|
}
|
|
}
|