# @podlite/markdown

=head1 Upcoming

=head1 0.0.63

=item the ESM build leaves declared dependencies to the consumer instead of inlining them. It used to resolve them by browser rules and bake in a character decoder that reaches for document, so importing the package from Node failed at load. The file went from 1.2 MB to 12 KB


=head1 0.0.61

=item a markdown heading takes its own text as the id instead of a generated one, so a link written against the heading reaches it

=head1 0.0.41

=item lift C<types> to top-level package field (was only in C<publishConfig>), add C<exports> map and explicit C<sideEffects>. Consumers can now resolve types without an ambient declaration

=head1 0.0.34

=item parse fenced code attributes into structured config items. C<```python :line-numbers :highlight<2,5-7> :caption<Example>> now produces the same AST as C<=code :lang<python> :line-numbers :highlight<2,5-7> :caption<Example>>, replacing raw C<:meta<string>> storage. Malformed attrs degrade gracefully — only C<:lang> survives. All value types (Bool/Int/String/List/Hash) supported via C<parseAttributes()> from C<@podlite/schema>

=head1 0.0.16

=item added alignment for column contents ( #9 )

=head1 0.0.14

=item avoid add `caption` element if title empty

=head1 0.0.12

=item implement inline `$...$` and block `$$...$$` formulas

=head1 0.0.9

=item implement `mermaid` support

=head1 0.0.7

=item `=markdown` now is standard block

=head1 0.0.6

=item refactor tests

=head1 0.0.5

=item refactor

=head1 0.0.4

=item fix export

=head1 0.0.3

=item update deps

=head1 0.0.2

=item update build

=head1 0.0.1

=item initial release