-
Notifications
You must be signed in to change notification settings - Fork 36
I upgraded from 0.4.0 to 0.4.5 and I get "Exited with code: 1" #32
Comments
@adamgins Is this still popping up for you? |
@johanbrook yep. I had upgraded to 0.4.5 , have not checked since.. |
I can't reproduce this. So weird. So there's no stack trace or anything? |
I can't see anything on the sever console. Is there some other log file /setting so I can get more detail?
|
I'm using 0.4.5:
|
Hm, Have you any idea of this, @chrisbutler ? |
opt-in SASS would be great, I really just want a few basic templates, I can go through the pain of writing old school CSS for a few emails. |
@adamgins can you give us more info on your system? @todda00 it's working for me using mupx on ubuntu 14.04.2 can you guys remove the emails package and just try installing @johanbrook making it somehow optional does seem ideal... but you'd probably have to do it as an addon package, like |
@chrisbutler |
@adamgins This package is set to be verbose as default (see this line), so that should be all info we got so far.
@chrisbutler Cannot something with weak dependencies be set up? For instance, detect that your SCSS package exists and load after it, and in code detect SCSS support. |
I do not have the emails package installed anymore, I add chrisbutler:node-sass only, and try to deploy with the same resulting error:
|
when I remove the chrisbutler:node-sass package it deploys perfectly. |
@todda00 can you update your node version? |
@chrisbutler Well meteor is stuck on node 0.10.X, so I upgraded it to 0.10.40 and got the same error. |
@todda00 there are some known/ongoing issues with node-sass. can you try following the suggestions here and see what you come up with? https://github.com/sass/node-sass/blob/master/TROUBLESHOOTING.md |
@chrisbutler the node-sass installs OK when I install it directly on the server via The only way I was able to get this to work was to install sass on the server via gems, and pull in the lookback:meteor-email package locally and remove chrisbutler:node-sass from package.js |
@todda00 @chrisbutler I've removed |
@johanbrook I found the issue. I had a rogue Wondering if we could have some better error logging, please? |
@adamgins Gotcha, I should take care of badly formatted templates better. Thanks! |
Sorry, I don't seem to have more info. If I re-install 0.4.0 it all works.
Were there breaking changes in code between those versions?
The text was updated successfully, but these errors were encountered: