Hyperblaster
Hyperblaster
Totally agree, we write this in to our own logic, but it makes sense that if an update is made it clears the cache entry
Hmm, i have some interesting ones. It often looks like the async_hooks is the cause of the blockage, is that correct? Or am i reading it wrong? ``` BLOCKED 439ms...
Same issue. The example seems to be a bit out of date with some pieces missing or looking to have changed.
Yeah, Async does not work for me at all.
@peterallan16 I'm struggling to get this to work due to the gaps in documentation, were you able to successfully get the package working?
Just hit this bug also! Such a pain in the neck. Rolling back to version 1.0.5 it works fine
Wouldn’t the expected behaviour be to throw an error? Currently it freezes the entite process or crashes the browser. In version 1.0.5 it works perfectly.
That makes sense. What is different between 1.0.5 and current version? > On 9 Apr 2018, at 6:18 am, Jeff Barnes wrote: > > I think expected result would be...
Any response to this? It works perfectly in 1.0.5 but crashes javascript 1.0.7
@huang-julien your code has helped us get our dynamic components rendering. However we're hitting one issue with templates failing to render that appears to be related: nuxt/nuxt.js#14314 I have a...