Skip to content

Releases: chawyehsu/saber

v0.12.2

16 Oct 15:07
2913812
Compare
Choose a tag to compare

🗡️Saber Alter

This is the 3rd public release of our forked edition of the discontinued Saber.

What's changed

  • Stopped passing Token constructor to markdown-it env. (9a59be4)
    • This might be a BREAKING CHANGE for plugins using the variable.
  • Changes primarily relervant to DX.
    • Types fixes. Fixed GitHub CI, ESLint, commit hooks, from jest to vitest, etc.

Full Changelog

To view all 81 commits from Saber Alter v0.12.1 to v0.12.2, please check out v0.12.1...v0.12.2

Migration Guide

See https://github.com/chawyehsu/saber/releases/tag/v0.12.0

There are 6 package published to npm for Saber Alter v0.12.2:

Metadata

Package size change:

v0.12.1

25 May 01:42
5960cbf
Compare
Choose a tag to compare

🗡️Saber Alter

This is the 2nd public release of our forked edition of Saber. It's released in May 2024.

What's changed

  • Nodejs version constraint node<17 was removed.
  • webpack has been upgraded from v4.46.0 to v4.47.0. (5960cbf)
    • This allows to remove the node<17 Nodejs version constraint, since md4 was backported to webpack v4.47.0.

Full Changelog

To view all 2 commits from Saber Alter v0.12.0 to v0.12.1, please check out v0.12.0...v0.12.1

Migration Guide

See https://github.com/chawyehsu/saber/releases/tag/v0.12.0

There were only 1 package published to npm for Saber Alter v0.12.1:

Metadata

Package size change:

v0.12.0

24 May 17:06
07dfccb
Compare
Choose a tag to compare

🗡️Saber Alter

This was the first public release of our forked edition of Saber. It was released in Aug 2023, with a goal of being a maintenance release.

What's changed

Since it's set to be a maintenance release, no criticial breaking changes were made in this release. That means basically all existing plugins/themes from the original community should work with Saber Alter v0.12.0. However, when we talk about "no criticial breaking changes were made", it's about the unchanged core API. There are some significant changes which are not relevant to the API may be considered as breaking changes, you may need to understand when considering migration.

Highlights

  • Nodejs version requirement is set to 16.x (node>=16 && node<17) (ffea25f) ! Consider BREAKING
    • webpack was upgraded from v4.42.1 to v4.46.0, yet it still relies on legacy crypto libraries which is deprecated starting from Nodejs 17. (f1164a2)
  • Babel stuff were removed (almost), babel-loader was replaced with esbuild-loader (c02c56e)
    • Legacy polyfills of object-assign and Promise were removed from the vue-app frontend (37394a5) ! Consider BREAKING
    • Since javascript transformation output has been targeted to es2015 in the esbuild-loader loader, the two polyfills were dropped without hesitation.
  • saber-highlight-css and saber-highlighter-prism were merged into saber-plugin-prismjs, that two packages were basically depended by saber-plugin-prismjs and the latter is the one users should depend on. (567b5af) ! Consider BREAKING
    • If you previously imported highlight CSS in your Saber theme from saber-highlight-css, consider migrating it to import from the new @alterjs/saber-plugin-prismjs plugin.
  • saber-utils and saber-log were integrated into the core for easier maintenance, the Core was written in ESM+TypeScript (not completely, and transformed to CommonJS in production though).
  • Although not all packages were published to npm, the version has been changed to be synced. (e3516a4)
  • No more node-gyp hell. (0e649a4)
  • saber eject-theme has been changed to use the native git command to download the theme. (e8c5b6e)
  • Much dependencies were upgraded to the latest working version without breaking existing stuff.
    • vue: 2.6.10 -> 2.6.14
    • markdown-it: 10.x -> 13.x
  • create-saber supersedes create-blog and create-site, for scaffolding new Saber Alter projects.

Full Changelog

To view all 74 commits from Saber v0.11.7 to Saber Alter v0.12.0, please check out [email protected]

Migration Guide

Because of the goal of this release, there shouldn't be difficult for users to migrate their projects from the original discontinued Saber v0.11.7 to Saber Alter v0.12.0.

Taking chawyehsu/chawyehsu.com as the reference, the migration was done in just one single commit: 92e0cf22. Basically you just need to replace saber with @alterjs/saber, and if you have used saber-plugin-prismjs, replace it with @alterjs/saber-plugin-prismjs (don't forget to migrate CSS imports mentioned above when it's the case).

There were only three packages published to npm for Saber Alter v0.12.0, except create-saber:

Metadata

Package size change: