Drop node 4 support
See original GitHub issueCurrently, it looks like CI builds are failing and I suspect they have been since updating to react 16 in #480.
After looking into this, it turns out enzyme swapped one of their dependencies scapel
for rst-selector-parser
which only supports node 5 and above. It also seems that node 4 is no longer active according to the node release schedule, so my question is can this repo drop support for node 4?
For further details see comments in #488.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Drop support for node 4 #4769 - facebook/jest · GitHub
Summary #4767 (comment) I'm thinking it's a good idea to do this separately from other changes which require node 4. (also ) Test...
Read more >Node4 Support | Contact Us
Please use the telephone numbers below to call us, or drop us an email if you'd prefer.
Read more >Remove a node type in Azure Service Fabric - Microsoft Learn
Learn how to remove a node type from a Service Fabric cluster running in Azure.
Read more >Cant delete and then create Node-RED Starter App - IBM
hi, i had an issue with my Node-RED Starter App where it kept crashing, so i decided to start all over by deleting...
Read more >Dell EMC PowerStore Installation and Service Guide for ...
CAUTION Because nodes include cooling fans, they should be removed for as short a time as possible. Do not remove nodes from a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like there might be a fix for this soon, see https://github.com/airbnb/enzyme/issues/1285
Here are some note from when i initially looked at this issue.
I am not against dropping Node v4, but we should look into supporting Node v7.