Skip to content

Commit 9996307

Browse files
ericgregoryvados-cosmonic
authored andcommitted
Update _posts/2026-03-19-five-ways-of-looking-at-jco-part-1.md
Co-authored-by: Victor Adossi <123968127+vados-cosmonic@users.noreply.github.com>
1 parent 77a8ef7 commit 9996307

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2026-03-19-five-ways-of-looking-at-jco-part-1.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ date: "2026-03-19"
55
github_name: "ericgregory"
66
excerpt_separator: <!--end_excerpt-->
77
---
8-
Jco is a ["multi-tool for the JS WebAssembly ecosystem."](https://github.com/bytecodealliance/jco) At the 2026 Bytecode Alliance Plumbers Summit, Technical Steering Committee member Bailey Hayes put it another way: Jco is "like five projects in one."
8+
Jco ([`@bytecodealliance/jco` on NPM](https://www.npmjs.com/package/@bytecodealliance/jco))is a ["multi-tool for the JS WebAssembly ecosystem."](https://github.com/bytecodealliance/jco) At the 2026 Bytecode Alliance Plumbers Summit, Technical Steering Committee member Bailey Hayes put it another way: Jco is "like five projects in one."
99

1010
It's certainly a project with many facets—five big ones, arguably! Recognizing what those facets are, and how they fit together, is the key to understanding why Jco matters beyond the JavaScript ecosystem.
1111

0 commit comments

Comments
 (0)