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

@esy-ocaml/flow-parser

v0.76.2

Published

esy package for flow-parser

Downloads

12

Readme

flow-parser

Build Status

Flow is a static typechecker for JavaScript. To find out more about Flow, check out flow.org.

This project is simply a repackaging of the Flow parser as an esy package for easy distribution on npm. Normally, there wouldn't be any need for this package, but here's why this exists:

  • Flow doesn't release new versions to opam frequently enough. It's very easy to make a new easy package that is more up to date and released to npm as an esy package.
  • Flow's release has a misconfigured META file.
  • This version makes use of dune namespacing to avoid module conflicts.

Versioning

The table below defines relationship between original Flow versions and @esy-ocaml/flow-parser (this package) versions.

flow orig version | @esy-ocaml/flow-parser version | If applying fixes to @esy-ocaml/flow-parser | ----------------------|----------------------------------|------------------------------------------ 0.76.0 | 0.76.0 | 0.76.1, 0.76.2, ... 0.76.1 | 0.76.1000 | 0.76.1001, 0.76.1002, ... 0.76.2 | 0.76.2000 | 0.76.2001, 0.76.2002, ...

This is done so we can release fixes to the original Flow Parser code which include build changes / dependency constraint changes and etc.

Consume As Library:

To consume this as a library, just add "@esy-ocaml/flow-parser" as a dependency of your esy project.

To Build / Test flow-parser Locally:

You need Esy, you can install the beta using [npm][]:

% npm install -g esy@preview

Then you can install the project dependencies using:

% esy install

Then build the project dependencies along with the project itself:

% esy build

And test compiled executable: esy x lets you run built binaries by name.

% esy x TestFlow.exe

License

Flow is MIT-licensed (LICENSE). The website and documentation are licensed under the Creative Commons Attribution 4.0 license (website/LICENSE-DOCUMENTATION).