Skip to content

Packaging. Testing. Ducks. Name a more iconic trio.

License

Notifications You must be signed in to change notification settings

stevenvelozo/quackage

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

50 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Quackage

Package. Test. Duck. Name a more iconic trio.

Who doesn't love managing configuration and tooling? I can tell you who doesn't love it. I don't love it.

This standardizes:

  1. Building an app for a browser
  2. Transpiling an app for ... older browsers
  3. Running unit tests

Usage

First you need to install the thing. The easy way is npm or whatever you use to get your packages, which installs the package and puts a couple commands in your node_modules/.bin folder. You run it either with quack or q for short.

npm install --save-dev quackage

Second, quack like a duck.

For instance, you can check your build configurations:

npx quack check-build

You can build the app

npx quack build

You can test

npx quack test

If you hate this, you can always inject commands into your package.json file:

npx quack enhance-my-package

About

Packaging. Testing. Ducks. Name a more iconic trio.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published