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

ezno

v0.0.23

Published

A JavaScript compiler and TypeScript checker written in Rust with a focus on static analysis and runtime performance

Downloads

135

Readme

Ezno

This contains a JavaScript edition of Ezno

CLI

This package includes a JS & WASM based version of the CLI. You can use as follows

node dist/cli.cjs info
# or
deno run -A dist/cli.mjs info

Library example

For a environment that supports node:fs, you can use a version that initializes the WASM for you

import { check } from 'ezno/initialised';
const fs_handler = (_path) => "const x: string = t ? 4 : 5;";
const output = check("input.ts", fs_handler);
console.dir(output.diagnostics, { depth: 5 });

For the web, init() is needed to load the WASM before calling any functions.

import { check, init } from 'ezno';

await init();

const fs_handler = (_path) => "const x: string = t ? 4 : 5;";
const output = check("input.ts", fs_handler);
console.dir(output.diagnostics, { depth: 5 });

See more usage in the ./test.mjs and in the playground.

You can see the Rust definitions of these exports under ../../src/wasm_bindings.rs. Thanks to #114 all these exports have associated type definitions.

There also exists more functions such as check_with_options which takes an additional TypeCheckOptions. For parsing string to AST there is parse_expression & parse_module. If you find something implemented in Rust, but not exposed to the JS or WASM context: feel to make a request issue for it to be exposed via the JS API.

Commands for building this package

Run this from this folder, not the root:

npm run clean
npm run build

See package.json for the other building commands.

  • It first builds the WASM binary with rustc, cargo build --lib --target wasm32-unknown-unknown
  • It then binds (builds associate JS library) into the build folder with wasm-bindgen --out-dir build --target web
  • It then bundles (and generates CJS & EJS formats) with some associate JS using unbuild into the dist folder