Handle escaped separators in split()

[DmitrySharabin]

Summary

split() honors \<sep> as an escaped separator: not split on, and the backslash is stripped from the yielded part. MapType.parseEntries() uses it for :-splitting.

Test plan

• npx htest test/split.js --ci
• npx htest test/PropType.js --ci

[LeaVerou]

I think since escaped colons are an older bug, they should remain separate. For the exports, I'm not sure this is the right fix. Can you commit the JSdoc fixes directly to types-refactor and slim this PR down to the colon handling fix?

[LeaVerou]

Can you commit the JSdoc fixes directly to types-refactor

Done

[DmitrySharabin]

slim this PR down to the colon handling fix

Done. After the type refactors PR is landed, we'll retarget it to the rollback-signals branch (if it won't happen automatically).

[netlify]

✅ Deploy Preview for nude-element ready!

Name	Link
🔨 Latest commit	3a603b4
🔍 Latest deploy log	https://app.netlify.com/projects/nude-element/deploys/6a184b2bd2aa310007a25177
😎 Deploy Preview	https://deploy-preview-128--nude-element.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[LeaVerou]

I think instead of handling this ad hoc, parseEntries() should be using split() which I believe handles escapes already (and if it doesn't, it should).