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@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.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@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";
  +import remarkCjkFriendly from "remark-cjk-friendly/parseOnly";
  +import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough/parseOnly";
  
   const processor = unified()
     .use(remarkParse)
     .use(remarkGfm)
     .use(remarkCjkFriendly)
     .use(remarkCjkFriendlyGfmStrikethrough)
     .use(remarkRehype)
     .use(rehypeStringify);

  If you only need the serialization functionality, you can import from remark-cjk-friendly/serializeOnly and/or remark-cjk-friendly-gfm-strikethrough/serializeOnly:

  -import remarkCjkFriendly from "remark-cjk-friendly";
  -import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough";
  +import remarkCjkFriendly from "remark-cjk-friendly/serializeOnly";
  +import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough/serializeOnly";
  
   const processor = unified()
     .use(rehypeParse)
     .use(remarkRehype, { allowDangerousHtml: true })
     .use(remarkCjkFriendly)
     .use(remarkCjkFriendlyGfmStrikethrough)
     .use(remarkStringify);

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";
  +import remarkCjkFriendly from "remark-cjk-friendly/parseOnly";
  +import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough/parseOnly";
  
   const processor = unified()
     .use(remarkParse)
     .use(remarkGfm)
     .use(remarkCjkFriendly)
     .use(remarkCjkFriendlyGfmStrikethrough)
     .use(remarkRehype)
     .use(rehypeStringify);

  If you only need the serialization functionality, you can import from remark-cjk-friendly/serializeOnly and/or remark-cjk-friendly-gfm-strikethrough/serializeOnly:

  -import remarkCjkFriendly from "remark-cjk-friendly";
  -import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough";
  +import remarkCjkFriendly from "remark-cjk-friendly/serializeOnly";
  +import remarkCjkFriendlyGfmStrikethrough from "remark-cjk-friendly-gfm-strikethrough/serializeOnly";
  
   const processor = unified()
     .use(rehypeParse)
     .use(remarkRehype, { allowDangerousHtml: true })
     .use(remarkCjkFriendly)
     .use(remarkCjkFriendlyGfmStrikethrough)
     .use(remarkStringify);

remark-cjk-friendly@2.1.0

Minor Changes

• f79f128 Thanks @tats-u! - Support HTML-to-Markdown path

Patch Changes

• 7f81e71 Thanks @tats-u! - docs(remark-*): clarify Rust-based Markdown/MDX compiler limitations in README

• Updated dependencies [f79f128]:

  • mdast-util-to-markdown-cjk-friendly@1.0.0

remark-cjk-friendly-gfm-strikethrough@2.1.0

Minor Changes

• f79f128 Thanks @tats-u! - Support HTML-to-Markdown path

Patch Changes

• 7f81e71 Thanks @tats-u! - docs(remark-*): clarify Rust-based Markdown/MDX compiler limitations in README

• Updated dependencies [f79f128]:

  • mdast-util-to-markdown-cjk-friendly-gfm-strikethrough@1.0.0

mdast-util-to-markdown-cjk-friendly@1.0.0

Major Changes

• f79f128 Thanks @tats-u! - Initial release

mdast-util-to-markdown-cjk-friendly-gfm-strikethrough@1.0.0

Major Changes

• f79f128 Thanks @tats-u! - Initial release