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

[dependabot]

Bumps the remark-cjk-friendly group with 2 updates: 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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

---

Note

Low Risk
Dependency-only bump affecting markdown rendering for CJK text; no auth or API logic changes, though lockfile churn is large.

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

The widget still imports the default entry points in markdown/index.tsx (no switch to /bidi or /parseOnly). Upstream 2.2+ adds optional subpaths for smaller bundles or explicit parse/serialize; behavior for default imports should stay compatible, with fixes such as exporting /bidi in 2.3.1.

The lockfile also reflects transitive resolution changes (e.g. Nitro nightly, Rollup 4, Babel 7.29.7) tied to the reinstall—not separate product changes.

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