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

create-flow-pkg

v1.0.10

Published

Create a Facebook Flow ready skeleton library or application with Babel

Downloads

16

Readme

create-flow-pkg

Create a Facebook Flow ready skeleton library or application with Babel

What this does

This is a skeleton project generator that will populate your new project with babel, eslint, jest, gulp and flow.

This will get you ready to start writing Flow enabled javascript in minutes.

This also sets up some package deployment task to move dist/ down to ./, so your import statements for sub files do not need dist/ (Only for Libraries)

Provides the following npm run <script> commands:

  • npm run node <src/file.js> - Runs with babel-register to compile on the fly
  • npm run lint - Runs eslint/flow checking
  • npm run start - Starts main for apps, or example for libraries
  • npm run example - Runs example (for libraries)
  • npm run distexample - Runs example using the dist/ compiled files (for testing production version)
  • npm run build - Runs babel to compile to dist folder for production readyness
  • npm run test - Runs Jest to run test suite

Requirements

Currently only tested in Linux(Ubuntu/Mint) but should work in any POSIX environment, Windows users, run inside of Git Bash or WSL.

Install:

sudo npm i create-flow-pkg -g

Usage:

In a new folder:

git init
git remote add origin [email protected]:your/repo.git
npm init
# for libraries designed for node only (no browsers)
create-flow-pkg initlib
# for libraries that also support browsers
create-flow-pkg initlib --browser
# for a node only app
create-flow-pkg initapp
  • initlib for libraries (Used by other libraries or apps),
    • Use --browser to activate more transforms
  • initapp for applications (Standalone programs / CLI scripts)

Requires yarn for now

Currently expects yarn to be installed. Will add interactive setup to choose yarn vs npm later.

sudo npm i yarn -g

Default node version

Default babel config targets node 6. Edit package.json to change this

  "engines": {
    "node": ">= 8.0.0"
  }

If you target 8, it will reduce the amount of transforms and only transform modules to commonjs

A few other transforms are avail

TODO:

  • Interactive setup asking to use yarn or npm
  • Upgrade existing install (init commands are destructive, do not use it on existing code base)