Infrastructure/astro
0
Fork 0
mirror of https://github.com/withastro/astro.git synced 2024-12-23 21:53:55 -05:00
Code Issues Activity
astro/packages/markdown-support/package.json

41 lines
1.1 KiB
JSON
Raw Normal View History

Use npm package names to load internal deps (#294) * 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
2021-06-04 13:19:01 -05:00
{
"name": "@astrojs/markdown-support",
Version Packages (#597) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2021-07-01 15:06:18 -05:00
"version": "0.2.0",
Use npm package names to load internal deps (#294) * 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
2021-06-04 13:19:01 -05:00
"main": "./dist/index.js",
Remark and rehype plugins (#562) * remark plugins * remove unused dependency * enable codeblocks * backward compatibility with remark-code-titles * add support for rehype plugins * add proper types for plugins * fixes after review - connect plugins by name - make plugins configurable - connect gfm and footnotes if no plugins provided from config - add more plugins to example * update and rename example * add documentation for markdown plugins * chore: rename with-markdown-plugins example * chore: restructure dependencies * feat: add back smartypants, fix mdx expressions * chore: remove log * test: add markdown plugin tests * chore: add changeset * docs: update markdown doc Co-authored-by: Nate Moore <nate@skypack.dev>
2021-07-01 11:55:22 -05:00
"type": "module",
Add repository remotes for all astro packages (#458) * Add repository remotes for all astro packages * Add repository.directory key instead of adding the path to repository.url * Include changeset * Add repository key to create-astro
2021-06-16 13:09:35 -05:00
"repository": {
"type": "git",
"url": "https://github.com/snowpackjs/astro.git",
"directory": "packages/markdown-support"
},
Use npm package names to load internal deps (#294) * 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
2021-06-04 13:19:01 -05:00
"exports": {
".": "./dist/index.js"
},
"scripts": {
"prepublish": "yarn build",
Update build script to avoid bundling (#304) * fix: simplify astro-scripts build * fix: remove source-map-support, add missing `.js` extensions * refactor: use `module` for `@astrojs/markdown-support` * fix: missing `.js` extension * fix: missed @astrojs/parser * fix: remove old file * fix: merge conflict * fix: CJS weirdness
2021-07-12 17:01:33 -05:00
"build": "astro-scripts build \"src/**/*.ts\" && tsc -p tsconfig.json",
Use npm package names to load internal deps (#294) * 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
2021-06-04 13:19:01 -05:00
"dev": "astro-scripts dev \"src/**/*.ts\""
},
Remark and rehype plugins (#562) * remark plugins * remove unused dependency * enable codeblocks * backward compatibility with remark-code-titles * add support for rehype plugins * add proper types for plugins * fixes after review - connect plugins by name - make plugins configurable - connect gfm and footnotes if no plugins provided from config - add more plugins to example * update and rename example * add documentation for markdown plugins * chore: rename with-markdown-plugins example * chore: restructure dependencies * feat: add back smartypants, fix mdx expressions * chore: remove log * test: add markdown plugin tests * chore: add changeset * docs: update markdown doc Co-authored-by: Nate Moore <nate@skypack.dev>
2021-07-01 11:55:22 -05:00
"dependencies": {
"@silvenon/remark-smartypants": "^1.0.0",
"gray-matter": "^4.0.2",
"mdast-util-mdx-expression": "^1.0.0",
"micromark-extension-mdx-expression": "^1.0.0",
"remark-footnotes": "^3.0.0",
"remark-gfm": "^1.0.0",
"remark-parse": "^9.0.0",
"remark-rehype": "^8.1.0",
"unified": "^9.2.1",
"unist-util-map": "^3.0.0"
},
Use npm package names to load internal deps (#294) * 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
2021-06-04 13:19:01 -05:00
"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"
}
}
Reference in a new issue Copy permalink