nightly builds of @swc/core are now available
In the future, we will build an ecosystem CI with it to ensure stability
Search for a command to run...
In the future, we will build an ecosystem CI with it to ensure stability
No comments yet. Be the first to comment.
We are thrilled to announce a major quality-of-life improvement for the entire SWC ecosystem. Starting from @swc/core v1.15.0, our Wasm plugins are now backward-compatible! Previously, developers using Wasm plugins often had to update them with each ...
Recently, I've been preoccupied with Wasm plugin compatibility issues in swc. I realized that backward compatibility would be difficult to achieve right now, so I decided to create a plugin registry that I had been putting off. The first thing that d...
CHANGELOG.md Full ChangeLog Bugfixes ES parser https://github.com/swc-project/swc/pull/8332 ES codegen https://github.com/swc-project/swc/pull/8346 https://github.com/swc-project/swc/pull/8351 ES: fixer pass https://github.com/swc-project/...
CHANGELOG.md Full ChangeLog Note: v1.3.98 is skipped because CI failed, and we want to keep git tags immutable. This is a very large release. So please check the links above.
CHAGNELOG.md Full ChangeLog This patch is mostly about the performance improvement. Bugfix: ascii_only: false PR: https://github.com/swc-project/swc/pull/8217 Performance improvements hstr instead of string-cache PR: https://github.com/swc-pro...
Today, we configured the build pipeline for nightly builds of @swc/core. You can try it by running the command below in your terminal.
# npm
npm i -D @swc/core@nightly
# yarn
yarn add -D @swc/core@nightly
# pnpm
pnpm i -D @swc/core@nightly
nightly builds are automatically published once per day, and we are going to prolong the release cycle of latest builds.
(Special thanks to GitHub and Microsoft, for sponsoring enormous amount of computing time for all OSS projects)
In the future, we are going to use this to improve the stability of @swc/core. The users can check if a newer version of @swc/core has a bug that can break their app, without building @swc/core by themselves. But this also applies to the core team. We are going to build a huge CI that runs periodically and check if the app breaks with the nightly version of @swc/core.
Honestly, I (DongYoon Kang ) wanted to add telemetry or automatic error reporting for unreachable!()s because they will help prioritize issues, but I think we will go with opt-in telemetry, even in case we add one.