engines config breaks deploys to Netlify about react-testing-library HOT 5 CLOSED

Yeah, I was mistakenly trying to run your validate script in react-testing-library on Node 6. Sorry for the confusion, lack of sleep and running on fumes today. 😄

from react-testing-library.

I'd be fine with 6. But why don't you upgrade to 8?

from react-testing-library.

In this particular case, I could, as Netlify provides a way to do that and I don't care about the Node version for my app. But I'd imagine scenarios exist where that's not possible, either due to lack of control of the runtime environment or app-specific target requirements or what-have-you. It seems like an odd and unexpected developer experience to require runtime environment changes to use such a small testing library when there's no underlying technical reason for it.

6 makes sense, I'll send a PR for it. Thanks!

from react-testing-library.

Oh. Just noticed kcd-scripts uses Object.entries. Thoughts? Maybe this truly does require Node 8.

from react-testing-library.

kcd-scripts shouldn't make any difference for whether you can use this library. This library doesn't depend on kcd-scripts (except as a dev dependency, which you shouldn't need to install). Now if you're using kcd-scripts yourself, then yes, you'll have to use Node 8. That will never support less than Node 8.

from react-testing-library.