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

jq-web-wasm

v0.5.3

Published

a hack that makes jq run in the browser with emscripten.

Downloads

331

Readme

jq-web-wasm

This is a fork of jq-web to support Node v18+ and TypeScript.

Usage

  1. Install

    npm i jq-web-wasm
    # or from Github
    npm i github:eGust/jq-web-wasm
    # or
    yarn add jq-web-wasm
    # or
    pnpm i jq-web-wasm
  2. Use with TypeScript

    // demo.ts
    import { assert } from 'node:console';
    import { promised } from 'jq-web-wasm/jq.wasm';
    
    const demo = async () => {
      const foo = await promised.json({ foo: 'bar' }, '.foo');
      const baz = JSON.parse(await promised.raw(JSON.stringify({ baz: 'bar' }), '.baz'));
      console.debug({ foo, baz });
      assert(foo === 'bar', `foo is not "bar" (got ${foo})`);
      assert(baz === 'bar', `baz is not "bar" (got ${baz})`);
    };
    
    demo();
    # run it in shell
    ❯ tsx demo.ts # [tsx](https://www.npmjs.com/package/tsx)
    { foo: 'bar', baz: 'bar' }

Motivation

Due to Node v18 introduced fetch API, the original jq-web uses fetch to detect whether it's running in a browser env. Unfortunately, this way no longer works since Node v18.

This package simply replaced typeof fetch === "function" with (typeof global !== 'object' && typeof fetch === "function") to get it work. In theory it should work for any version that support WASM. However, Node v14 is almost reaches its EOL, so I put the engine to require Node >= 16.

Compile by yourself

Please check scripts in package.json:

  1. run pnpm i to install dependencies.
  2. run pnpm copy-wasm-to-dist to copy jq.wasm.wasm to dist/.
  3. run pnpm reformat:jq.wasm.js to generate readable dist/reformatted-jq.wasm.js.
  4. update dist/reformatted-jq.wasm.js and replace dist/jq.wasm.js with it.
  5. run pnpm minify to create dist/jq.wasm.min.js

Sure you can use npm or yarn instead.