-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
engines config breaks deploys to Netlify #12
Comments
I'd be fine with 6. But why don't you upgrade to 8? |
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! |
Oh. Just noticed |
|
Yeah, I was mistakenly trying to run your |
feat: 🎸 add allAtOnce optiont to type()
react-testing-library
version: 1.4.0node
version: 6.13.1npm
(oryarn
) version: yarn 0.18.1Relevant code or config:
react-testing-library
package.json
:What you did:
react-testing-library
todevDependencies
What happened:
Problem description:
react-testing-library
uses a somewhat restrictiveengines
stanza inpackage.json
Suggested solution:
react-testing-library
to4.5
(fromkcd-scripts
babel config) or at least6
(active LTS)?The text was updated successfully, but these errors were encountered: