fix: ensure all custom container characters are properly handled

[andreww2012]

Resolves #266

This PR ensures all custom containers characters are internally marked as consumed within micromark so that "expected character to be consumed" assertion is not triggered when using the dev bundle.

How to test

NODE_OPTIONS='--conditions development' tests/src/language/extensions/custom-container.ts

[changeset-bot]

⚠️ No Changeset found

Latest commit: dcca2d9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Try the Instant Preview in Online Playground

ESLint Online Playground

Install the Instant Preview to Your Local

npm i https://pkg.pr.new/eslint-plugin-markdown-preferences@f0e5fc2

Published Instant Preview Packages:

• eslint-plugin-markdown-preferences: https://pkg.pr.new/eslint-plugin-markdown-preferences@f0e5fc2

View Commit

[ota-meshi]

Thank you for the PR!

Can you add a job to your CI workflow that tests that environment?
(Please use the latest version of node etc.)