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

o-parsed-js

v3.0.2

Published

Javascript expression tree visitor, on top of esprima parser

Downloads

1

Readme

ParsedJS

A standard Javascript expression tree visitor, on top of esprima parser

It relies on esprima to parse a Javascript expression, and it provides a visitor to walk through the expression tree

Also, it defines a basic model of Javascript class and method definitions

It's not an introspection model, as it operates on static source code, but it allows for static source code inspection and edition

Installation

npm install o-parsed-js

Documentation

http://o-programming-language.org/

Usage

ParseTreeVisitor subclass

Create a subclass of ParseTreeVisitor

As an example, the class below parses expressions to perform simple arithmetical operations

const { ParseTreeVisitor } = require('o-parsed-js')

class Calculator extends ParseTreeVisitor {
  doesHandleExpressionType (treeNodeType) {
    const allowedExpressionTypes = [
      'BinaryExpression',
      'ExpressionStatement',
      'Literal',
      'Program'
    ]
    return allowedExpressionTypes.includes(treeNodeType)
  }

  evaluate (text) {
    return this.parseAndVisitString(text)
  }

  visitBinaryExpression (binaryExpression) {
    const left = this.visit(binaryExpression.left)
    const right = this.visit(binaryExpression.right)

    switch (binaryExpression.operator) {
      case '+':
        return left + right
      case '-':
        return left - right
      case '*':
        return left * right
      case '/':
        return left / right
      default:
        throw new Error(`Uknown operator ${binaryExpression.operator}`)
    }
  }

  visitExpressionStatement (expressionStatement) {
    return this.visit(expressionStatement.expression)
  }

  visitLiteral (literal) {
    if (!Type.isInteger(literal.value)) {
      throw new Error(`Uknown expression ${literal}`)
    }
    return literal.value
  }

  visitProgram (program) {
    return this.visit(program.body[0])
  }
}

const calculator = new Calculator()
calculator.evaluate('1+2') === 3

and implement the visit methods of interest

Stylist

Not stable yet

Don't use it, unless you have a test coverage of 100%

Javascript, class oriented, source code styler, to release programmers from caring about the format of the source code they write

Write the method, then run stylist

It'll re-arrange each method source code, to a uniform style, no matter who wrote it

I'm writting it as a replacement of eslint, for I want a class oriented parser

Also, it might set the grounds to, in a future, improve it with custom refactor rules, specific to object oriented code in javascript

Runs with

npx stylist