CDN: Empty Results about express-cdn HOT 8 CLOSED

Ok, apparently one needs to actually include a CDN call from an asset for the plugin not to crash on production mode. Building upon that I'm getting another error after adding this line:

!= CDN("/stylesheets/vendor/bootstrap.css")

to my main base jade layout. Now I'm getting an "unsuccessful upload" error.

Working on this right now.

from express-cdn.

Ok, this is good to be closed.

from express-cdn.

I'm having the same problem. Error: CDN: empty results isn't a very helpful error. @niftylettuce if you give me some details on what causes that error then I can probably make a PR.

from express-cdn.

I was just getting this issue and started digging into it.

@leostera was basically right. The thing is, my variable definition was "cdn" and not "CDN". express-cdn looks for the latter with a regular expression.

The error makes sense now but perhaps it would be wise not to hardcode "CDN" in there.

from express-cdn.

same thing happened to me.

from express-cdn.

@leostera @thebyrd @mateusz- see release 0.1.4 in NPM

from express-cdn.

@leostera I am getting the same unsuccessful upload error with all the same configuration options - what was your solution? Here is what I am getting:

│info:  task=express-cdn, message="css/app.css" was not found on S3 or was modified recently
│unsuccessful upload of image "" to S3
│unsuccessful upload of image "" to S3
 ....
│unsuccessful upload of image "ng" to S3
│
│events.js:71
│        throw arguments[1]; // Unhandled 'error' event
│                       ^
│Error: write EPIPE
│    at errnoException (net.js:770:11)
│    at Object.afterWrite (net.js:594:19)

from express-cdn.

@imrane @leostera have you resolved this? please report back ASAP need to make sure this works, thanks guys!

from express-cdn.