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

typescript-plugin-safescript

v0.6.3

Published

This TypeScript Plugin allow to transform JavaScript Runtime to apply type checking at Runtime for performing implicit coercion

Downloads

13

Readme

TypeScript Plugin for SafeScript Runtime

This package intent manipulate AST to enforce type checking at runtime

How it is different from Babel Plugin for SafeScript Runtime

Consider the following example:

const str0 = "3124122";
const num0 = 9;
const str1 = "3124122";
const num1 = str1 - num0;
const num2 = 55 + num1;
const num3 = 5 + num0;
const num4 = (num3 + 1) + 8;
let num5 = 3;
num5 += "3";

let str2 = "24256";
let numstr2 = +str2;

++numstr2;

function something(num) {
    if (typeof num === "number") {
        return num + 88;
    }
    return num + 88;
}
something(2);

Babel Plugin will generate the following file:

const str0 = "3124122";
const num0 = 9;
const str1 = "3124122";
const num1 = SafeScript.sub(str1, num0);
const num2 = SafeScript.add(55, num1);
const num3 = SafeScript.add(5, num0);
const num4 = SafeScript.add(SafeScript.add(num3, 1), 8);
let num5 = 3;
num5 = SafeScript.add(num5, "3");

let str2 = "24256";
let numstr2 = SafeScript.plus(str2);

(numstr2 = SafeScript.inc(numstr2));

function something(num) {
  if (typeof num === "number") {
    return SafeScript.add(num, 88);
  }
  return SafeScript.add(num, 88);
}
something(2);

As you can see Babel Plugin changed each operator, because it do not have information about types for expressions and variables

Lets check what will generate TypeScript Plugin:

const str0 = "3124122";
const num0 = 9;
const str1 = "3124122";
const num1 = SafeScript.sub(str1, num0);
const num2 = 55 + num1;
const num3 = 5 + num0;
const num4 = (num3 + 1) + 8;
let num5 = 3;
num5 = SafeScript.add(num5, "3");

let str2 = "24256";
let numstr2 = SafeScript.plus(str2);

++numstr2;

function something(num) {
    if (typeof num === "number") {
        return num + 88;
    }
    return SafeScript.add(num, 88);
}
something(2);

As you can see TypeScript Plugin inserted only 4 checks at runtime instead of 10 for Babel Plugin. It is because TypeScript Plugin knows type of each expression and variable at any place in code and it could decide if runtime check is needed