* Make astro package play nice with node16 module resolution
Projects using node16 module resolution in typescript uses the new
exports and imports configuration from typescript to find definition
files. This mirrors how nodejs resolves the files. If a package contains
an exports map in the package.json, typescript will ignore the "types"
field (not sure how it plays with typesVersions). This moves the typings
hirearchy of definition files into the same hierarchy that astro
produces output files in, so that typescript can discover them.
Fixes: #4172
* Add changeset
* Reorder export keys
* Update paths inside .d.ts files
Co-authored-by: Princesseuh <princssdev@gmail.com>
* Renamed getHeaders() to getHeadings(), according to RFC #208.
* chore: update changeset
* fix: expose MarkdownHeading type from `astro`
Co-authored-by: Félix Sanz <me@felixsanz.com>
Co-authored-by: Nate Moore <nate@astro.build>
* Move client types into Astro
* Adds a changeset
* Fix path to local client
* Reference vite/client in our HMR types
* Add back in the expect-error
* Update types comment
* feat: add rawContent obj with html helper
* refactor: change toString to function call
* test: rawContent helpers
* chore: update MarkdownInstance type
* refactor: parseHtml -> html
* chore: changeset
* fix: remove needless async heading on content version
* fix: fixLineEndings helper on unit tests
* refactor: change api to raw and compiled
* chore: add new type to env.d.ts
* docs: JSdocs for raw and compiled
* refactor: change API AGAIN to rawContent, compiledContent
* chore: update changeset
