astro - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2021-06-16	Version Packages (#466)	github-actions[bot]	2	-1/+7
	Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2021-06-16	Add repository remotes for all astro packages (#458)	Caleb Jasik	1	-0/+5
	* 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-04	[ci] yarn format	matthewp	1	-0/+1

2021-06-04	Version Packages (#295)	github-actions[bot]	2	-1/+7
	Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2021-06-04	[ci] yarn format	matthewp	2	-2/+2

2021-06-04	Use npm package names to load internal deps (#294)	Matthew Phillips	7	-0/+199
	* 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