Mike Chau

I was able to resolve this by adding the line `config.assets.precompile += %w( store/print.css )` to application.rb, so it should look like: config.assets.initialize_on_precompile = false config.assets.precompile += %w( store/print.css )...

@jalberto seems to be related to issue: https://github.com/spree/spree_fancy/issues/2 You can follow a suggestion by @aaronzdavis for https://github.com/spree/spree_fancy/issues/2#issuecomment-17148318 if you do not want to precompile locally every time when deploying to...

Thanks! I plan to be adding the ES6 version as well. Probably after I finish Part 2. My application is still on `0.12.x`, but I plan to update the document...

Hi @arkadyp do you have links for the ones that appear to be broken? Thanks for the comments! If you like, you can create a new JS Bin and under...

That would be great! However, in that example, I do see a the content div.  But I do see that by default this JS Bin has `Auto-run JS` unchecked,...

I've ran into this issue as well... yeah it's a very weird bug! I'll definitely make a note about it in my next update.

That's interesting! Should I wait till all the parts are completed or do you think its worthwhile to incrementally publish?

We were just bitten by this bug, noticed a large amount of memory usage and this was from workers failing to stop when we redeploy. :( How are you handling...