Jason Walton

A few random thoughts about this: First, our objective is to build an isomorphic app, so we want to render an HTML page on the server which contains fully rendered...

@BinaryMuse A slight suggested variation on what you've got going on in https://github.com/BinaryMuse/isomorphic-fluxxor-experiment/. Instead of throwing away the initial result from the first server side render, just return it. The...

Well, the obvious API would be to return an array if there's more than one... But this is terrible from a "breaking the API" perspective. You could add a `{multi:...

I also have no idea how signed cookies would work here. I'd guess you'd have to check the cookie against every signature?

RFC 6265 says: > Although cookies are serialized linearly in the Cookie header, servers SHOULD NOT rely upon the serialization order. In particular, if the Cookie header contains two cookies...

Oh, I see, the signature is a custom thing. Yeah, so you can't rely on order - you just have to check them all. And yes, key rotation is going...

@raqystyle yes, exactly - one has the "foo.server.com" domain, and one has the ".server.com" domain (meaning it's sent to any server in *.server.com). Unfortunately, the client doesn't bother to send...

I published a fork with this fixed: https://www.npmjs.com/package/@benbria/react-selectize

I've actually been using @sinonjs/fake-timers with @testing-library/[email protected], @testing-library/[email protected], [email protected], and [email protected] quite successfully - I had no idea I wasn't supposed to. Upgrading to the latest @testing-library with the new...

> It would make more sense for jest to allow different fake timers implementations. What if you want to use this library with mocha? Or with some other non-jest test...