Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial checklist
Description of changes
Hi! Some highlights of the first month back into open source, and in this year: January!
I’m back for a while! After a month away. And also after half a year with Rust stuff.
syntax-tree
(which is the lion’s share of complexity), and particularly solved TS 4.9, but also improved a lot of docs, JSDocs, types,null
handling, updated deps and actions, tests to usenode:test
andnode:assert/strict
, and narrowed down which types are exposed.parse-english
and friends, updated{hast,mdast}-util-to-nlcst
for themparse5
version*-select
(Failing test: Comma selectors are evaluated independently syntax-tree/unist-util-select#14)hast-util-to-text
(Add failing test case for new-lines syntax-tree/hast-util-to-text#3)hast-util-raw
(RAWTEXT/RCDATA elements are closed inconsistently syntax-tree/hast-util-raw#19)xast
(some info in: https://github.com/rgrove/parse-xml/commits/next)vscode-mdx
, most props definitely go to him thoestree-walker
, most props definitely go to him thoFor next month, I’ll do vfile/micromark/prep unified (2 weeks?).
Then I want to really update micromark to backport Rusty fixes, change things around. Which will result in breaking changes everywhere (maybe a month?).
I’ve also been preparing
To do: next major
comments in a bunch ofsyntax-tree
utilities, e.g., removing overloads, not returning passed reference values, and returningundefined
instead ofnull
. I think it’s good to do these too.And then remark/rehype/retext should be smooth majors, but good to do quickly, but anyway we’re talking March now?