HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
swc-project
swc
Rust2018–2025
swc-project / swc

swc

Rust-based platform for the Web

Web DevelopmentLanguages & Compilers
Explore on GitHubRead Hacker News discussions
50Distinct people
50Mentions
1Explicit recommenders
34.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Rust-based platform for the Web

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Slightly tangential, but I can't tell if I love or hate the logo for swc https://github.com/swc-project/swc Either way, I want to try this next time I'm using TypeScript.

dj_gitmo used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:03:49 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year50 dated mentions

Observed mentions: 2018-11-10 20:18:20 UTC to 2025-09-16 12:14:36 UTC.

051015202018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 3 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 18 mentions; 2 submissions, 16 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC431
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC10010
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC18216
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC918
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Make the web (development) faster. SWC (stands for Speedy Web Compiler) is a super-fast TypeScript / JavaScript compiler written in Rust. It's a library for Rust and JavaScript at the same time. If you are using SWC from Rust, see rustdoc and for most users, your entry point for using the library will be parser. Also, SWC tries to ensure that If you select the latest version of each crates, it will work for rust users. MSRV of crates is currently 1.73. To update all SWC crates you use, you can run curl https://raw.githubusercontent.com/swc-project/swc/main/scripts/update-all-swc-crates.sh | bash -s. This script will update all dependencies to the latest version and run cargo build to ensure that everything works. Note that you need jq cargo upgrade command to run the script. Supported Node Versions: Node v10+ for usage Node v20+ for development If you are using SWC from JavaScript, please refer to docs on the website. Documentation Check out the documentation in the website. Native npm packages use self-loading compressed addons on x64 and arm64 macOS, Windows MSVC, and Linux GNU/musl. The first load materializes the verified original addon; package names and JavaScript APIs stay the same. See native addon carriers for the supported-target boundary and SWC_NATIVE_BINDING_CACHE. Features Please see comparison with babel. Performance Please see benchmark results on the website. Supporting development Supporting swc Star History Powered by Sponsors SWC is a community-driven project, and is maintained by a group of volunteers. If you'd like to help support the future of the project, please consider: Giving developer time on the project. (Message us on Discord (preferred) or Github discussions for guidance!) Giving funds by becoming a sponsor (see https://opencollective.com/swc)! Contributing See CONTRIBUTING.md. You may also find the architecture documentation useful (ARCHITECTURE.md). License SWC is primarily distributed under the terms of the Apache License (Version 2.0). See LICENSE for details.
Read the full README on GitHub

What Hacker News says

18 sources
fabiospampinato·Sep 21, 2021
I'd argue the JS engine in browsers is _also_ built for JS developers, and even though we are definitely a minority compared to all the internet users it's important to underline that most of the stuff currently available online, for better or for worse, wouldn't exist without developers writing it. Like the average user in fact couldn't care less about what languages websites are written in, but if browsers shipped only a brainfuck compiler I'm sure there would be a lot less development happening on the web, in some sense JS developers are the target users of JS engines. I think this is literally the first time that I hear anybody saying that TypeScript is very fast. It's no coincidence that the top open issue in Deno's repo is literally titled "TypeScript compiler in Rust" [0]. The developer behind swc is even rewriting the whole type c
Read the rest
hecker in TypeScript [1]. A lot of people, myself included, think that TS can get excruciatingly slow, in a large-enough but not really huge codebase, in a way that probably wouldn't happen if it were written in something like Rust with a big focus on performance. [0] https://github.com/denoland/deno/issues/5432 [1] https://github.com/swc-project/swc/issues/571
In Rome will be written in Rust
lhorie·Sep 21, 2021
esbuild is the current darling leading the pack, but there are also various other projects in the space (swc[0] is written in Rust, fjb[1] is written in C, bun[2] is written in zig, leveraging JavascriptCore's engine). The most significant performance-oriented effort in this space still leveraging JS that I know of is kataw[3], and while that's quite fast compared to babel, it's still within an order of magnitude from babel. Kataw itself is a CST-based implementation that was created to outperform seafox (a AST-based parser by the same developer), which itself is an iteration over several other perf-oriented parser projects. Babel gained popularity due to the crazy amount of churn in grammar over the past few years, but more and more I think the dust is settling, and flexibility is no longer the name of the game, making an AST-based imple
Read the rest
mentation less appealing. The Rome team must be feeling the heat if the data structure design choices are being informed by performance. I highly doubt someone will be able to compete in performance using a JS implementation in today's landscape. [0] https://github.com/swc-project/swc [1] https://github.com/sebbekarlsson/fjb [2] https://bun.sh/ [3] https://github.com/kataw/kataw
In Rome will be written in Rust

Showing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.