Skip to content

Conversation

@nex3
Copy link
Contributor

@nex3 nex3 commented Apr 6, 2021

There's no reason we should have to do this, since we do declare
support for Chokidar 3.0.0 and npm should just install the latest
available version that matches the constraint. But in practice it
doesn't for some reason, so I guess we'll narrow the constraint to
work around that.

See #863

There's no reason we *should* have to do this, since we do declare
support for Chokidar 3.0.0 and npm *should* just install the latest
available version that matches the constraint. But in practice it
doesn't for some reason, so I guess we'll narrow the constraint to
work around that.

See #863
@nex3 nex3 requested a review from Awjin April 6, 2021 20:47
@nex3 nex3 merged commit 16d6711 into master Apr 15, 2021
@nex3 nex3 deleted the chokidar branch April 15, 2021 22:49
@silviuburceadev
Copy link

I can't be more happy now that chokidar 2.x doesn't block me upgrading to Node.js 14.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants