The devDependency browserify was updated from 16.4.0 to 16.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

browserify is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I'm getting this (below) when trying to pipe the tests into testron. I'm having trouble finding anyone else with the same issue via google searches. You can see the SHA I'm on, with my npm/node versions in the screenshot:

I also tried Node v0.12 with no luck.

Ever bumped into this?

The API, functionality and even code look very similar.

What we need and what’s not there in insert-css are three things:

• https://github.com/substack/insert-css/pull/16
• https://github.com/substack/insert-css/pull/17
• https://github.com/substack/insert-css/pull/18

The reason: tape-css. There’s some more background in the PRs themselves.

The devDependency tape was updated from 4.9.2 to 4.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency browserify was updated from 16.3.0 to 16.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

browserify is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency standard was updated from 13.1.0 to 14.0.0-1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

standard is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Would be cool if the function would return an object with an indication if the cache has been hit or not... something like

{
   cached: boolean
}

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

I have no idea why, but the v1.2.0 publish is broken. There's no index.js in the package downloaded from npm.

I made a fork of insert-css that allows changes to existing CSS files to insert style contents into the same style element instead of creating a new one.

Then I made it so each time I insert styles via my transform, I pass in the filename as the id: https://github.com/ajoslin/stylin/blob/master/index.js#L67

This makes it so hot module reloading works: A reload of a JS file referencing a CSS file will cause the newest styles to be inserted into an existing <style> tag.

It's hopeless to submit a PR to substack's insert-css, that project is unmaintained (~10 open PRs, some years old).

Here's what I would like:

• Allow id to be passed in to insert-styles, similar to my fork of insert-css
• Change stackcss to use insert-styles: sheetify and css-extract.
• Have sheetify pass a filename, if given, as the id to insertStyles.

And now finally, hot module reload would work perfectly with the sheetify stack.

cc @yoshuawuyts

I can do all of the PRs if these ideas sound "OK" to you two.