chore:update engine requirements
we should probably raise an issue on fdir, since i'm pretty sure they want to remain compatible with node12. i'll merge this if they don't want to keep node12 compatibility
we should probably raise an issue on fdir, since i'm pretty sure they want to remain compatible with node12. i'll merge this if they don't want to keep node12 compatibility
oh
I don't think fdir still wants to support a node version from 6 years ago, even node 14 support was debated last year. I think this should be discussed in their open issue about the engines field: https://github.com/thecodrr/fdir/issues/116
@godky considering fdir hasn't removed their usage of AbortController and it's been two weeks (with no one reporting any issues) i might merge this. were you affected by fdir breaking node 12 support?
@godky considering fdir hasn't removed their usage of
AbortControllerand it's been two weeks (with no one reporting any issues) i might merge this. were you affected by fdir breaking node 12 support?
@SuperchupuDev Yes, some of our CI environments used node12 and encountered errors, so we upgraded the node version.
fyi i've posted a pinned issue talking about a possible engines update to >=16.0.0 #134
fdir is restoring node 12 support for its next release, as such this won't be needed anymore. thank you for the pr anyways :+1: