• 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.