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

tweed-cli

v0.5.0

Published

CLI for Tweed

Downloads

16

Readme

CLI for Tweed

Installation

$ npm install --global tweed-cli

Creating a new Tweed project

Without configuration, new projects will be installed with Webpack and Babel, and scripts will be added to package.json for building for production (npm run build) and running a development server (npm run dev).

Before doing anything, the CLI will ask if you're satisfied with the options, so you can try different flags and options safely.

$ tweed new blog
? Here's what I got:

Project Name: blog
Directory:    ./blog
Bundler:      Webpack
Compiler:     Babel
Task Runner:  NPM scripts
Test Runner:  none
Linter:       none

Is this correct? (Y/n)

There are other options, though. You can turn stuff off:

$ tweed new blog \
  --bundler none \
  --compiler none \
  --task-runner none
? Here's what I got:

Project Name: blog
Directory:    ./blog
Bundler:      none
Compiler:     none
Task Runner:  none
Test Runner:  none
Linter:       none

Is this correct? (Y/n)

With this configuration, boilerplate will use ES5 JS and no tooling will be installed.

TypeScript

Run tweed new --compiler typescript to install TypeScript tooling and use the language for boilerplate.

Running tasks with a Makefile

Run tweed new --task-runner make to put the scripts in a Makefile instead of NPM scripts.

Test Runners

Use tweed new --test-runner jest|mocha to install one of those test frameworkers, as well as some boilerplate.

Linters

Use tweed new --linter standard to install a linter for Standard JS.

Generating components

Use tweed generate to create new components quickly.

$ tweed generate MyClass
Generated src/MyClass.js

The command will use hints from the environment to figure out if you're using TypeScript or Babel. Otherwise it generates ES5 components.

You can add mutating fields to the components using the --mutating option.

$ tweed generate Counter --mutating count --mutating otherField -m thirdField
Generated src/Counter.js

If you're using TypeScript, you can provide the types of the fields by separating with a colon:

$ tweed generate Counter --mutating count:number
Generated src/Counter.tsx

To simultaneously create directories, namespace the component with periods or slashes:

$ tweed generate pages.start.StartPage
Generated src/pages/start/StartPage.js

$ tweed generate data/Repository
Generated src/data/Repository.js

Add --test to generate a corresponding test case. Given that you have installed either Jest or Mocha (e.g. tweed new --test-runner jest):

$ tweed generate pages.start.StartPage -t
Generated src/pages/start/StartPage.tsx
Generated __tests__/pages/start/StartPage.test.tsx