This release contains a nicer scaffolding dialog and will abort without writing files (see #73, thanks @filtercake):

You can now pass a github token to Pingy CLI. This will help if you're rate limited on the Github API. Get a Github Personal Access Token here You can do this in two ways:

1. Add "githubToken" key to your global config file at ~/.config/configstore/@pingy/cli.json:

{
  "githubToken": "961990a44422b5a9b07279a1d7c70949c5fXXXXX"
}

2. Create a PINGY_GITHUB_TOKEN environmental variable

export PINGY_GITHUB_TOKEN=961990a44422b5a9b07279a1d7c70949c5fXXXXX

You will need to set the token if you see this error:

Pingy CLI now supports custom scaffolds!

See: #35.

Usage: scaffold [options] <url>

Scaffold a new website using a third-party project template


Options:

  --yarn          Use Yarn instead of NPM for installing packages
  --global-pingy  Don't install local version of Pingy CLI, use global version instead
  -h, --help      output usage information

<url> can be:

• Git URL: https://github.com/pingyhq/pingy-scaffold-bootstrap-jumbotron.git
• Shorthand GitHub URL: pingyhq/bootstrap-jumbotron
• Filesystem path: /Users/dave/code/pingy-scaffolds/bootstrap-jumbotron

So a typical scaffold command would be pingy scaffold pingyhq/bootstrap-jumbotron

If you are interested in creating your own scaffold then here are some instructions. You can also join me in the new Gitter chat channel for some help. I've also created a reference scaffold: bootstrap-jumbotron.

• npm install --save-dev @pingy/[email protected] to update/install local version
• npm install --global @pingy/[email protected] to update/install global version

• Descendants of script[type=module] now cause a reload (#61)
• Update express-autoprefixer (https://github.com/gustavnikolaj/express-autoprefixer/pull/18)

• Default to pingy.json, instead of .pingy.json (Closes #57)
• Remove Chokidar dependency and replace with fs.watch (Closes #56)
• Better CLI output on export errors
• Fix for invalid source map path '$stdin' (Fix #15)
• Fix for autoprefixer running twice on compiled files

• Fixed bug where export didn't respect sourceMap: false from .pingy.json.
• Lots of 3rd-party dependency updates

• Bugix: Files didn't get scaffolded if you choose the 'same options as last time' option
• Lots of under-the-covers changes in preparation for custom scaffolds support

• Don't prompt for export folder name, just assume 'dist' (can still be configured in .pingy.json)
• Remember last settings used and allow quick initialisation of new projects using existing settings
  
• npm install --save-dev @pingy/[email protected] to update/install local version
• npm install --global @pingy/[email protected] to update/install global version

• Fix for write after end error [instant] (#27)

• Lots and lots of minor bug fixes
• End-to-end (command-line to browser) tests that work on Mac, Windows & Linux
• Autoprefixer CSS support (#9)
• npm install --save-dev @pingy/[email protected] to update/install local version
• npm install --global @pingy/[email protected] to update/install global version

• Added typescript to pingy init

Features

1. Support globally installed modules (Re: #8)

Just add globalModuleSearch to your .pingy.json.

{
  "name": "my-site",
  "foo": "bar",
  "globalModuleSearch": true
}

Bugfix

Document root not being served if it's compiled. Fixes #44.

Features

• Add Yarn install support. You can now do pingy init --yarn to install packages with Yarn instead of NPM. (#26)

Features

• Detect existing package.json and ask user to confirm if they wish to continue (#29)

Fixes

• Add script object to package.json if none exist (fixes #32)
• Use tab-indentation for package.json

Features

• Switch to npm init --yes (#18)

Fixes

• Live reload on change of Pug/Jade Partials bug (#19)
• LESS mapping doesn't work in Chrome DevTools bug (#30)
• 'path' -> 'upath' (#31)
• Options in .pingy.json are now respected (mentioned in #34)

What's New

• Added pre-release autoprefixing support

How do I install

You can install it using:

npm install @pingy/cli@next

Note the @next at the end because I want more people using it before I release to the main channel.

Notes

To enable autoprefix then just add the following entry to your .pingy.json:

{
  //...
  "autoprefix": true,
  //...
}

This will default to autoprefixing for the last 2 browser versions if set to true. But you can also set it to a string or an array of strings (e.g.. ["> 5%", "last 1 version"]). More info on available queries here.

Remaining Issues

If you're using Less/Sass/Stylus/etc.. then you don't need to worry about the following, it is only an issue for those using vanilla (no-compiler) CSS.

If you're using vanilla CSS then autoprefixing won't work for pingy dev, it will only work for pingy export. This is due to the way that I have architected Pingy CLI internally to serve uncompiled files directly from disk. More time is needed to re-architect Pingy CLI and get this working cleanly.

Reporting Bugs

If you are having issues related to autoprefix support then please comment on this issue.