Dominik Ferber

Thanks for your nice report! Maybe using `path.join` could work? So something like `const postcssRunner = path.join(__dirname, "postcss-runner.js")` could do the trick?

Interesting! I haven't used web components myself, so I'm not very helpful here. A wild guess is that this line might not catch the HTML when a web component is...

Hmm, I don't recall whether it's possible. It's been a while since I made this package and I'm not actively using it anymore. Feel free to send a PR!

Thanks for sharing your findings. I vaguely remember dealing with `waitUntilNetworkIdle` to ensure the page is completely loaded before taking the screenshot. Otherwise you could get discrepancies more often due...

Thanks for the hint @peterjosling! iirc, the puppeteer api had a breaking change. If we make it a peer dep, we should update our puppeteer usage to ensure we can...

Thanks for reaching out! This package was an experiment a while ago and I'm a bit surprised by the growing usage :) I started using TypeScript since writing it. A...

`flagBag.setCookie(response)` would be a nicer way of handling this. Then we can drop `flagBag.cookie.args`.

On further thought having `useFlags` render `` would happen too late. At that point the real request could start already (unless using SSR). Should we export a `` component instead...

Thanks for your input here! Your suggestion has valid points, some of which happykit already supports and some that gave me new ideas :) ## On feature flags vs waiting...

Thanks for all that context, that's great! I think what you want out of happykit is definitely possible without too much effort! It would require me exposing the flag definitions...