chore(deps): bump the remark-cjk-friendly group across 1 directory with 2 updates

[dependabot]

Bumps the remark-cjk-friendly group with 2 updates in the / directory: remark-cjk-friendly and remark-cjk-friendly-gfm-strikethrough.

Updates remark-cjk-friendly from 2.0.1 to 2.3.1

Release notes

Sourced from remark-cjk-friendly's releases.

remark-cjk-friendly-gfm-strikethrough@2.3.1

Patch Changes

• 7b08850 Thanks @​tats-u! - fix(remark-*): add /bidi entry point to package.json

  The /bidi entry points were advertised as available starting from v2.3.0, but they were not actually exported in package.json, so users could not use them.

  With this fix, the /bidi entry points are now officially available for use. If you want to use both parsing and serialization, please update your import statements to use the /bidi entry points as shown below:

  -import remarkCjkFriendly from "remark-cjk-friendly";
  -import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough";
  +import remarkCjkFriendly from "remark-cjk-friendly/bidi";
  +import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough/bidi";

remark-cjk-friendly@2.3.1

Patch Changes

• 7b08850 Thanks @​tats-u! - fix(remark-*): add /bidi entry point to package.json

  The /bidi entry points were advertised as available starting from v2.3.0, but they were not actually exported in package.json, so users could not use them.

  With this fix, the /bidi entry points are now officially available for use. If you want to use both parsing and serialization, please update your import statements to use the /bidi entry points as shown below:

  -import remarkCjkFriendly from "remark-cjk-friendly";
  -import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough";
  +import remarkCjkFriendly from "remark-cjk-friendly/bidi";
  +import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough/bidi";

remark-cjk-friendly-gfm-strikethrough@2.3.0

Minor Changes

• 9371983 Thanks @​tats-u! - feat(remark-*): add new entry point /bidi

  I may have made a design mistake in v2.1.0—most users only needs parsing, but I added serialization as an opt-out, increasing the bundle size by a few KB. For the next major version upgrade, I may introduce a breaking change to enable only parsing (currently /parseOnly) unless a subpath is specified, just like in v2.0.1 or earlier, in a future release. To prepare, I've added a new entry point /bidi for users using both parsing and serialization. I recommend updating your import statements now:

  -import remarkCjkFriendly from "remark-cjk-friendly";
  -import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough";
  +import remarkCjkFriendly from "remark-cjk-friendly/bidi";
  +import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough/bidi";

  If you're a user who has been using these plugins since v2.0.1 or earlier and don't particularly care about bundle size, feel free to import them either with or without the /parseOnly suffix.

Patch Changes

... (truncated)

Commits

• b064617 Version Packages (main) (#52)
• c79aa56 Merge branch 'main' of github.com:tats-u/markdown-cjk-friendly
• 7b08850 fix(remark-*): add /bidi entry point to package.json
• 27d9fa7 Version Packages (main) (#51)
• 4b135b8 chore: approve some safe task commands in Copilot
• 9371983 feat(remark-*): add new entry point /bidi
• 3d003d1 docs(README,remark-*): update related packages in README
• 22418e8 Version Packages (main) (#50)
• 05e7a04 feat(remark-*): add new entry points /parseOnly & /serializeOnly
• f1d6cc0 build(deps): bump the npm_and_yarn group across 1 directory with 2 updates (#49)
• Additional commits viewable in compare view

Updates remark-cjk-friendly-gfm-strikethrough from 2.0.1 to 2.3.1

Release notes

Sourced from remark-cjk-friendly-gfm-strikethrough's releases.

remark-cjk-friendly-gfm-strikethrough@2.3.1

Patch Changes

• 7b08850 Thanks @​tats-u! - fix(remark-*): add /bidi entry point to package.json

  The /bidi entry points were advertised as available starting from v2.3.0, but they were not actually exported in package.json, so users could not use them.

  With this fix, the /bidi entry points are now officially available for use. If you want to use both parsing and serialization, please update your import statements to use the /bidi entry points as shown below:

  -import remarkCjkFriendly from "remark-cjk-friendly";
  -import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough";
  +import remarkCjkFriendly from "remark-cjk-friendly/bidi";
  +import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough/bidi";

remark-cjk-friendly-gfm-strikethrough@2.3.0

Minor Changes

• 9371983 Thanks @​tats-u! - feat(remark-*): add new entry point /bidi

  I may have made a design mistake in v2.1.0—most users only needs parsing, but I added serialization as an opt-out, increasing the bundle size by a few KB. For the next major version upgrade, I may introduce a breaking change to enable only parsing (currently /parseOnly) unless a subpath is specified, just like in v2.0.1 or earlier, in a future release. To prepare, I've added a new entry point /bidi for users using both parsing and serialization. I recommend updating your import statements now:

  -import remarkCjkFriendly from "remark-cjk-friendly";
  -import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough";
  +import remarkCjkFriendly from "remark-cjk-friendly/bidi";
  +import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough/bidi";

  If you're a user who has been using these plugins since v2.0.1 or earlier and don't particularly care about bundle size, feel free to import them either with or without the /parseOnly suffix.

Patch Changes

• 3d003d1 Thanks @​tats-u! - docs(remark-*): update related packages in README

  Good news: this doesn't change any functionality.

remark-cjk-friendly-gfm-strikethrough@2.2.0

Minor Changes

• 05e7a04 Thanks @​tats-u! - feat(remark-*): add new entry points /parseOnly & /serializeOnly

  Added new entry points for both remark-cjk-friendly and remark-cjk-friendly-gfm-strikethrough packages, allowing users to import only the parsing or serialization functionality as needed. This change helps reduce bundle size for users who only require one of the functionalities.

  When you want to use only the parsing functionality, or if you have been using these packages since v2.0.1 or earlier, you can now import plugins from remark-cjk-friendly/parseOnly and/or remark-cjk-friendly-gfm-strikethrough/parseOnly:

  -import remarkCjkFriendly from "remark-cjk-friendly";
  -import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough";

... (truncated)

Commits

• b064617 Version Packages (main) (#52)
• c79aa56 Merge branch 'main' of github.com:tats-u/markdown-cjk-friendly
• 7b08850 fix(remark-*): add /bidi entry point to package.json
• 27d9fa7 Version Packages (main) (#51)
• 4b135b8 chore: approve some safe task commands in Copilot
• 9371983 feat(remark-*): add new entry point /bidi
• 3d003d1 docs(README,remark-*): update related packages in README
• 22418e8 Version Packages (main) (#50)
• 05e7a04 feat(remark-*): add new entry points /parseOnly & /serializeOnly
• f1d6cc0 build(deps): bump the npm_and_yarn group across 1 directory with 2 updates (#49)
• Additional commits viewable in compare view

---

Note

Low Risk
Dependency-only bump with no application code changes; main follow-up risk is possible bundle-size or markdown-behavior shifts from the upgraded remark plugins, not security or auth paths.

Overview
Bumps remark-cjk-friendly and remark-cjk-friendly-gfm-strikethrough in convai-widget-core from 2.0.1 to 2.3.1, with matching pnpm-lock.yaml updates.

The lockfile reflects upstream wiring changes: new transitive mdast-util-to-markdown-cjk-friendly* packages and mdast-util-from-markdown@2.0.3. No import paths or markdown pipeline code in this repo are changed; the widget still imports the default package entry points in markdown/index.tsx.

^{Reviewed by Cursor Bugbot for commit d7d1148. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit acd9b4c. Configure here.}