Thomas Hallock

> I'm not sure why, but the plugin see it differently when you're calling a method from `props` or if your acessing a `property` from `props`. @cbdeveloper the reason is...

> why use this package over the native node one? For rendering the components server-side. Even if it doesn't make sense to use a web worker on the server, it's...

@dancrumb You can use the `

@evanplaice

> I don't understand the purpose of this PR glad you asked :) > Why switch all the tests to Jest? 1. In removing the validator from the public export,...

> This PR has a ton of cross-cutting concerns, which will lead to merge conflicts leading up to 1.0. The only impact here is in the test code, so unless...

> The validator appears in everything up to 1.0 pre-releases. If the validation/test updates were isolated into a separate PR that work could be backlogged until the work on pre-releases...

> Popular != modern. jest is modern compared to tape. > Jest is popular for FrontEnd testing b/c it comes with JSDOM and a ton of other features. jest is...

> Cross-cutting concerns = README.md, there's other cleanup work that still needs to take place there. ok, let's get that taken care of as well. Do you have a work...

>>> resume-cli should be switched over before resume-schema is bumped > 1.0 there. >> >> didn't we do that yesterday? > > On the `master` branch, yes. The change still...