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

v4fire-cli

v1.0.16

Published

Tools for creating V4Fire blocks and pages from CLI

Downloads

18

Readme

WIP V4Fire-cli

Tools for creating V4Fire blocks and pages from CLI

v4fire -h

Usage

Make block

TBD

Rename block

TBD

Make test

v4fire make-test src/base/b-slider

You can generate test files for both component and module. The tool also will take care of updating demo-page dependencies and adding new test cases to test cases file.

For both component and module the tool generates test/index.js file that performs basic test setup and executes simple test.

In case of module test, the tool relies on b-dummy component designed specifically for testing purposes.

Runners

You can specify which runners you want to be included in test directory. By default, there are no runners and all test code locates in the test/index.js file. So if you'd like to have different runners for your test cases, you can specify them just after the path to module or component being tested.

v4fire make-test src/base/b-slider analytics render events

For each specified runner the tool will create test/runner/runner-name file. Here is the example of runner template for a module.

In this case generated test/index.js file will include only test setup and all test evaluation code will be moved to runners.