After deploy, COMPONENT_CSS_LOOKUP keeps old component ids until a hard reload causing much havoc

So I’m still trying to make sense of how this is happening, but I thought it was worth posting this sooner rather than later cause it’s causing me some serious headaches.

After each deploy to my production environment (using divshot), everything seems to come down the pipe alright (updated hashes for all the assets, the app still works and most of my styles work). However, anything that was styled by a component style has no styles at all. It will stay this way through refreshes as well. The only thing that will fix it is a hard reload. So obviously something is being cached somewhere, I just don’t understand what yet.

The reason there are no styles on components is that values injected in the vendor js for the component ids (COMPONENT_CSS_LOOKUP) have different ids than the ones that are actually in the stylesheets (ie: the lookup has page-header-376c34f9 but my css has page-header-8fa991a4)

I’m still trying to wrap my head around how this addon works but my hunch right now is that this problem may be related to PR #76

So I have two questions:

1. is there anything else I can provide?
2. Why the guid? It feels superfluous as the component name is unique enough.

[ebryn]

Fixed as of 0.2.0-beta.1

[ryansch]

That’s an excellent question. I’m still new to ember-land and we have plans to manually namespace our component styles.

I just happened to find a workaround for this package. You might want to try pinging a maintainer.