npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

glass-swc

v2.0.1

Published

glass swc plugin

Downloads

32

Readme

This README is for developers of glass (not normal users of it). Get in touch if you have any questions! [email protected].

publishing the package

  1. increment package.json's version number FIRST!!

To build the .wasm file, run these two commands (or npm run build): 2. run cargo build --target wasm32-wasi --release - this generates the .wasm file using Rust 3. run cp ./target/wasm32-wasi/release/glass_swc.wasm . - this copies the wasm file to the root where package.json expects it

To publish the package to npm (the entry point of the package is the .wasm file), do this: 4. run npm publish --access public

updating and versions

The @swc/core npm package used in the user's frontend needs to be compatible with the .wasm file generated here.

There's something to do with making versions of @swc/core (npm, package.json) match versions of swc_core (cargo, Cargo.toml), here, but it seems fine to use the latest version of swc_core (and I'm not sure if @swc/core is even used at all anywhere).

Just a helpful note, run npm show @swc/core version and cargo search swc_core to get the latest versions.

versioning notes

^1.6.2 means 1.6.2 thru (excluding) 2.0.0

~1.6.2 means 1.6.2 thru (excluding) 1.7.0

1.6.x means 1.6.0 thru (excluding) 1.7.0