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
4. Copying files around
5. Managing package.json files in a standad way
6. Assembling folders of JSON views into v7iew classes
7. Boilerplate files and file structures
8. Pulling documentation from codebases
9. Compiling data description language files into their downstream parts (manifests, sql generation, documentation, etc.)

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

Related Packages

• indoctrinate - Documentation scaffolding

License

MIT

Contributing

Pull requests are welcome. For details on our code of conduct, contribution process, and testing requirements, see the Retold Contributing Guide.