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-js

v1.3.7

Published

The relevant directories are `glass-react`, `glass-swc`, and `vscode-extension`.

Downloads

358

Readme

Glass

Explanation

The relevant directories are glass-react, glass-swc, and vscode-extension.

The other directories are irrelevant (babel-extension is not used, and www is a Next.js project that renders what you see on https://useglass.ai).

Running

  1. Add glass_swc.wasm to your config:
// next.config.js
const nextConfig = {
    experimental: {
        swcPlugins: [
            ['glass-js/swc', {}],
        ],
    }
}

Or if you want to use the development version on your own computer:

// next.config.js
const nextConfig = {
    experimental: {
        swcPlugins: [
            ['PATH/TO/glass/glass-swc/dist/glass_swc.wasm', {}],
        ],
    }
}
  1. Add <GlassProvider /> to your app.
import GlassProvider from "glass-js";

Or if you want to use the development version on your own computer:

import GlassProvider from "PATH/TO/GlassProvider";
  1. Run the vscode extension either through the VSCode marketplace, or opening vscode-extension inside a separate VSCode window and pressing F5.

Building

To get started developing, run these steps:

Run pnpm install to install everything. We use pnpm instead of npm because we're a monorepo and pnpm is more efficient, but it works exactly the same as npm.

Run npm run build:all to build both the Glass React bar and the Nextjs swc plugin (this just runs npm run build in both folders).

You don't have to do anything more unless you want to edit the extension. If you want to edit the extension, cd into vscode-extension and run npm install (we disabled pnpm in vscode-extension because most vscode docs use npm instead).

Publishing

You can publish two things:

  1. Contents of the vscode extension (from vscode-extension) to the VSCode marketplace.

  2. The <GlassProvider /> package (from glass-react) together with the SWC plugin (from glass-swc) to npm.

To publish vscode extension, it's like publishing any other vscode extension. Run vsce publish.

To publish the the npm package, run npm run publish. Make sure to increment the version number in the relevant package.json or you'll be rejected. Look at the command for more details, but in short it publishes only the built files.