Jason Miller

I'm still confused how it's possible to end up with `props.children` containing values like `null` or `undefined`. Preact strips those out - see this demo: https://jsfiddle.net/developit/z97ua3m3/ So it would seem...

Looks like it might be related to props.children bring an empty array. Does this happen outside the demo when not extending a shared class?

I think this might be fixed as of preact 7.1?

@ruiaraujo nice! anything else with Blueprint having issues? If not we can close this issue out 🎉

Ahh sorry, that makes sense. Here's hoping the issue was similar and they are both fixed :)

Alright, thanks for testing @sceutre!

Nope! There have been a whole bunch of releases since the last comment though, it's very possible this is no longer an issue.

Hi there! It looks like your aliasing on the server is actually not taking effect - you can tell because there are React internals included in the stack trace you...

@mikestead are you aliasing outside webpack to handle that then? interested to know how that works.

nice!