Andy Wermke
Andy Wermke
JSON tasks should be able to use `$1`, `$2`, `$NODE_ENV`, ...
There should be something like `launch --link` that updates the local `package.json`. Writes something like this to `package.json`: ``` js "scrips": { "build": "launch build", "test": "launch test" } ```...
Two different use cases to consider: ## "text/plain": Use different rendering if not in a TTY (if piping output into a log file, build server, ...) - Don't show fancy...
Like grunt/gulp/... So you can use different versions of npm-launch in multiple projects.
Change default config file name according to current [postcss-loader](https://github.com/postcss/postcss-loader) conventions.
Host webdebugger with sample data using gh-pages, so people can try the interface without installing the package.
Let's come up with a neat icon for postcss-debug!
To make it easy to quickly try postcss-theme there should be some minimal working sample for reference.
Hi, I would really appreciate to have two separate tasks for serving and compiling, independent of `harp.server.server` config.
Reason: There is no require('connect').utils.serializeCookie() anymore. Solution: Change the call require('connect').utils.serializeCookie(...) [Line 603] to serializeCookie(...) and declare the following function (taken from an old connect version): ``` js var serializeCookie...