micromark-util-resolve-all is a core utility package within the micromark ecosystem, designed to facilitate the complex process of resolving subtokens that cannot be parsed in a straightforward left-to-right manner. This is crucial for Markdown constructs such as attention (e.g., strong and emphasis) and media (links and images), where opening and closing delimiters might be matched non-sequentially or need post-processing after initial tokenization. The package is currently at version 2.0.1 and is part of the micromark project, which typically sees frequent, granular updates across its many utility packages, often released in lock-step with micromark's major versions. As an internal utility, it's not typically intended for direct end-user consumption but rather for developers extending micromark's parsing capabilities. Its primary differentiator is its role in orchestrating the event manipulation necessary for correct CommonMark parsing of non-linear syntax structures.
npm install micromark-util-resolve-allVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to use the `resolveAll` function by providing mock micromark events, constructs, and context. It shows how `resolveAll` orchestrates custom resolvers within constructs to process and transform the event stream, crucial for parsing non-linear Markdown syntax elements.
Migrate your project to use ECMAScript Modules (ESM) with `import` statements, or stick to a previous major version if CommonJS is strictly required (though older versions might not be compatible with newer micromark releases).
Upgrade your Node.js environment to version 16 or newer. Refer to the Node.js official documentation for upgrade instructions.
Unless you are developing a custom micromark extension at a very low level, consider using micromark's higher-level APIs or existing extensions instead of this utility directly.
Ensure your project is configured for ESM, using `import` statements and setting `"type": "module"` in your `package.json`, or explicitly using `.mjs` file extensions. For Node.js, ensure you are running a compatible version (16+).
No dependency data recorded yet.