& seems to be encoded?

[zykeee]

When parsing from markdown to html like:

import rehypeSanitize from "rehype-sanitize"
import rehypeStringify from "rehype-stringify"
import remarkParse from "remark-parse"
import remarkRehype from "remark-rehype"
import { unified } from "unified"

const md = "&"
const processed = unified()
	.use(remarkParse)
	.use(remarkRehype)
	.use(rehypeSanitize)
	.use(rehypeStringify)
	.processSync(md)
	.value.toString()

console.log(processed)

The result is <p>&#x26;</p>, seems to be encoded; but for others like ', works just fine.
Is this an expected behavior and why if it is?

[wooorm]

Yes, the way things are, is expected.
There are many options, which you can use to configure things.
See for example https://github.com/rehypejs/rehype/tree/main/packages/rehype-stringify

[zykeee]

Thanks for your reply.
I haven't found an option to change this behavior, what fits my scenario is to get <p>&</p> instead of <p>&#x26;</p>.
So what I do is to add .replaceAll("&", "&") after processing it.

[wooorm]

This is an XY problem.

You do not need to do that.

Please ask about what your actual goals are

[zykeee]

You are right.
I just notice that the gap here is browser would render <p>&#x26;</p> correctly as '&' but the lib I'm using would not. (react-pdf-html)
So when I pass the parsed html to it, it shows &#x26 like:

[wooorm]

Right, so that sounds like a bug there: if it accepts HTML, it should accept character references (which is the name for these things).

Your flow of things might not be optimal: you use these tools to generate a string of HTML, and then parse that HTML, and turn it into React.
I am sure there are tools that can instead turn markdown into PDFs directly, or through React, but without the serialized HTML in between!