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

boldr-cli

v0.1.10

Published

Commandline interface for Boldr

Downloads

30

Readme

Boldr CLI

The CLI for Boldr allows quick scaffolding of a new Boldr project.

Commands

Init

boldr init <dir>

Creates a new Boldr project. Requires a directory name as the input.

Usage: boldr init newProject
Installation would be <Current Working Dir>/newProject

Dev

boldr dev

Starts the development process. In order for the dev command to work, boldr-plugin-webpack must be installed.

Usage: NODE_ENV=development BOLDR_PORT=3000 BOLDR_DEV_PORT=3001 boldr dev

Build

boldr build

Starts the production compiling process. In order for the build command to work, boldr-plugin-webpack must be installed.

Usage: NODE_ENV=production boldr build

Clean

boldr clean <dir>

Clean compiled Boldr files, the cache and optionally a specified directory. The directory cleaning, assumes the path of the folder you wish to remove starts from the current working directory.

Usage: boldr clean test/tmp
The following would be removed:

 <Current Working Dir>/node_modules/.boldr_cache
 <Current Working Dir>/dist/assets/*
 <Current Working Dir>/dist/server.js
 <Current Working Dir>/dist/server.js.map
 <Current Working Dir>/test/tmp

Component

boldr component <NAME>

Generate a new component and the related files.

index.js
Foo.js
Foo.test.js
Foo.scss

src/shared/components/Foo

Options

-s, --stateless Stateless function component

-d, --directory Specify the directory for the component. The default directory is ./src/shared/components/

-c, --css-extension <css|less|sass
Use a different style type. The default for Boldr is scss.

-t, --test <jest|none> Choose between jest or none. A Jest test file is automatically created by default.