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

lazy-babylon-to-estree

v1.1.0

Published

Lazily transform a Babylon AST into an ESTree AST. Only transforms nodes that are accessed

Downloads

7

Readme

lazy-babylon-to-estree

CircleCI

WIP: Lazily "convert" a Babylon AST to the ESTree equivalent. Currently only converts Literals. For the time being, the goal of this project is only to support the bare minimum transformations needed by webpack.

Features

  • Conversions happen lazily when a property on the AST is accessed
  • Original AST is not mutated (besides 1 non-enumerable, symbol-keyed prop on the Program node)
  • Referential Equality between nodes is maintained (===)
  • Transformations occur as other code traverses the tree (this module does not perform a separate traversal of the AST)

Why?

This is an experiment I'm doing with webpack and babel-loader to try and prevent the double parsing of code, without having to create an entire transformed copy of the AST each time we go from babel-loader >> webpack. It's possible this will have no positive performance impact (or will even have a negative perf impact), but I'd never know if I didn't write the code 🕺.

Missing Features/TODO

  • ObjectProperty and ObjectMethod >> Property
  • ClassMethod >> MethodDefinition