@imnotjames do you have any ideas why this small change could fail a CI?

npm/cli#558

In particular

npm/cli#558 (comment)

npm v7 won't have this problem. (I'm working in the code that'll do this now.) I haven't checked into how involved it'd be to fix this issue for npm v6, but there's a good chance it'll just end up being "upgrade to v7 for the fix". In the meantime, I'd recommend using npm install instead of npm ci if this is affecting you.

This is likely because we upgraded fsevents or updated the lockfile on a machine which needed it.

We also probably want to use lock-verify to ensure the lockfile is in sync with the package list.

I'll take a look at a PR later today to try to resolve it. #6571

Awesome. Looks like we're all good to go!

Oh - one little thing for the future - this would be a test change rather than a chore change

https://github.com/typeorm/typeorm/blob/master/CONTRIBUTING.md#commit

It's a bit confusing to find the right one sometimes. I'll update the title for ya!

Thanks for the contribution 🎉