Brad Carleton
Brad Carleton
Yea this is a socket.io thing.
I think you want to leave the log level alone, I think it defaults to "debug: 3". You might open up a javascript console and see there is any other...
Yea, that's what I'm saying. I don't think the request is ever making it to your application code. I think it might be getting stopped by dotcloud's load balancer. So...
Yea, I just checked out your url and it looks to be nginx, which I don't think support websockets on dotcloud. Hope that helps!
I am definitely open to this. But I don't really want to break backward compatibility. What if there was just an option to provide your own compiler lib to the...
I actually think the way I'm doing it is a little more correct. Because for connect-asset they say to do something like this: ``` js npm install stylus ``` Well...
Yea, that's doable, but are you gonna be upset that I'm also doing a `require('nib')` in there? If that's sufficient then great, I think you can override the nib stuff...
It's now on the roadmap! Cheers!
Dynamic assets are cool, there is an `options` object for the individual assets: ``` js new DynamicAssets({ type: StylusAsset urlPrefix: '/style', dirname: './style', options: { libs: { stylus: require('stylus'), nib:...
I'm not opposed to going the more modular route if that's what people think is best, but I would have to bump the major version for that. I believe auto-override...