Josh Coldsmith

I second this issue. From what I have found in [this stackoverflow question](https://stackoverflow.com/questions/55230628/is-there-a-way-to-speedup-npm-ci-using-cache) it seems that `npm ci` doesn't really benefit from cache and that is by its design. `npm...

Any update on this? This feels at best like a bug that should be fixed soon and at worst CircleCI intentionally deceiving its clients to make more money.

I second that this would be really nice to have!

My team and I are also facing the same issue as @gentksb.

@joezappie I found [this solution](https://lit.dev/playground/#gist=242f45fd2dbe21ecb6902f144686aae8) to work very well for me. You can find the full comment [here](https://github.com/lit/lit/issues/4602#issuecomment-2023714335).

You're welcome! To be clear I didn't create that solution but I found it [here](https://github.com/lit/lit/issues/4602#issuecomment-2023714335)

@enkelmedia Thank you for this very helpful solution! On my end this solution works but I am seeing a pretty noticable flickering when dragging items around due to the DOM...

Actually after doing some more searching I found that this workaround actually does the trick with much less code and no screen flickering! https://lit.dev/playground/#gist=242f45fd2dbe21ecb6902f144686aae8

Update! While this still does seem like a bug, my workaround was to import `app-configuration.js` at the top of `katapult-maps-desktop.js` instead of it being imported using a script tag. 

We are also experiencing this issue still on `13.5.0`. [Issue 2800](https://github.com/firebase/firebase-admin-node/issues/2800) makes it seem like this problem is fixed, but it is not.