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

vfe-cli

v1.4.17

Published

vfe build cli, base on webpack & gulp.

Downloads

16

Readme

vfe-cli

npm version

vfe-cli is command-line interface for vfe

Usage

Install cli

npm install vfe-cli -g

Init project using vfe-template

vfe init [template]

Note: Using proxy option, vfe init -p $proxy. Such as vfe init -p tx. See $tx

vfe init support 3 types template:

  • default An simple boilerplate that using vfe as component builder only.
  • client The boilerplate is appropriate for client-side render project. It use Zect as components framework.
  • node The boilerplate is appropriate for server-side render project. It use Real and comps.
  • spa The boilerplate is appropriate for that project which using client-side render and hash router without reloading. Components framework use Zect and router use Routed.
  • autonode Autonode template.

Run default build task

vfe

Start develop watcher

vfe start
## aliase
vfe s

Note: Start command support run with another task name, such as vfe start sometask, only if task name is start-sometask.

Releasing for production

vfe release
## aliase
vfe r

Note: Release command support run with another task name, such as vfe release sometask, only if task name is release-sometask.

License

MIT.