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

@vanportal/van

v0.11.0-alpha.3

Published

Vanportal CLI toolkit.

Downloads

6

Readme

@vanportal/van

Vanportal CLI toolkit.

Usage: van <command>

Commands:
  van babel       Babel with our opinionated defaults               [aliases: b]
  van eslint      ESLint with our opinionated defaults              [aliases: e]
  van serverless  Serverless with our list of supported plugins   [aliases: sls]
  van webpack     Webpack with our opinionated defaults             [aliases: w]

Options:
  --help     Show help                                                 [boolean]
  --version  Show version number                                       [boolean]

Examples:
  van eslint .
  van babel --help
  NODE_ENV=production van webpack src -o dist.js

External tools

These useful tools are also included as peerDependencies without the van wrapping, execute directly with npx <NAME>:

node_modules/.bin
├── babel-node -> ../../../../node_modules/@babel/node/bin/babel-node.js
├── concurrently -> ../../../../node_modules/concurrently/bin/concurrently.js
├── eslint -> ../../../../node_modules/eslint/bin/eslint.js
├── jq -> ../../../../node_modules/@vanportal/van/bin/jq
├── js-yaml -> ../../../../node_modules/js-yaml/bin/js-yaml.js
├── nodemon -> ../../../../node_modules/nodemon/bin/nodemon.js
├── npm-check -> ../../../../node_modules/npm-check/bin/cli.js
├── sort-package-json -> ../../../../node_modules/sort-package-json/index.js
├── van -> ../../../../node_modules/@vanportal/van/bin/van.js
├── webpack -> ../../../../node_modules/webpack/bin/webpack.js
└── webpack-cli -> ../../../../node_modules/webpack-cli/bin/cli.js

0 directories, 11 files

Features

  1. All-in-one development dependency
  2. Execute <command> at current working directory
  3. Load our defaults if no configurations found at current working directory
  4. By default load .env and export to <command> through process.env
    1. Load .env.dev or .env.prod if NODE_ENV is set to development or production
    2. Load .env.${NODE_ENV} otherwise
    3. Variables from .env will NOT override those already set in environment