Have you seen #12209 (comment)?

I definitely saw it when it was posted but forgot about it. Closing since they're working on it and will probably do a better job than me :)

See #12209

I would love to help out if you decide to continue this PR and have any questions. My first suggestion is: add remark-gfm

@j-f1 I think I have made great progress here now.

In this PR, let's focus on the markdown parsing, I kept the mdx parser untouched, it still using unified@9 and remark-parse@8.

I've created remark-11 branch, let's merge this one into it, and then start working on the mdx parser, then we merge together into main branch.

@seiyab Thanks for the liquid plugin from #16134

We still need go through the test changes to make sure they are right.

I'm not going to continue work on this recently. Welcome to continue the work or review if interested. @j-f1 @seiyab @remcohaszing @tats-u

ac15218 (#13676) can find all the code used in other commits.

Thank you for your work.
I'm wondering how can we manage that which format changes are valid and which ones are invalid well...

The AST_COMPARE test can test if the AST changed. Eg: https://github.com/prettier/prettier/actions/runs/9626611049/job/26552757384?pr=13676#step:6:2509

Sounds good! But maybe some wrong parsing can be missed? (technically unchanged wrong AST can exist)

I would put some faith in the parser that it produces correct ASTs.

@fisker
I'm considering make changes to let FULL_TEST=1 yarn test ./tests/format/markdown pass.
But this branch j-f1:upgrade-remark is in forked repository, not prettier/prettier. How should we propose changes? Is just creating branch from j-f1:upgrade-remark and submitting PR against prettier:remark-11 directly fine?

submitting PR against prettier:remark-11 directly fine?

You can do that

I'm sorry but I'm not working on this now.
Feel free to tackle this if someone is interested in it.

Continue in #18277