Chris Cowan
Chris Cowan
+1, but the option should be spelled properly. *Colour*.
This is a duplicate of https://github.com/kriskowal/asap/issues/55 which was fixed.
I've noticed that adding a `.` on the same line before the apostrophe is sometimes responsible for triggering this.
I found a thread-safety issue that I believe could cause this issue sometimes and fixed it in #60. There was no synchronization between the reads of StatusManager in handling the...
I investigated this issue a bit and I think there's two parts to it: 1. https://github.com/alephjs/aleph.js/issues/446, which is an issue common to all CSS files. 2. When a CSS module...
I have trouble figuring out what's going on from the video. Can you compare your code against what your browser's devtools think the page's code is?
I can't reproduce this issue in Browserify-incremental 3.0.1 or the current version. package.json ``` json { "name": "foo", "version": "1.0.0", "description": "", "main": "foo.js", "dependencies": { "babelify": "^7.2.0", "browserify": "^13.0.0",...
I personally wouldn't expect the tool to do first-time setup like this on the same command that's used for routinely updating the dnslink record. If I hadn't seen this thread,...
Right. (Well it most likely wouldn't be a CNAME, but just A/AAAA root records pointing to my server.)
I believe that part of the readme about browser support is just referring to that they started using ES2015isms like `const` and discontinued their UMD build which could work in...