The PR is so huge I think because the lock was generated with npm7+; I think the old lock was npm 6 (so lock version 1); maybe redo this with npm 6 to prevent churn?

Regenerated the lock file using npm@6

Related: #46931

Might want to revert those changes when you're pinning chalk anyway.

Hm, perhaps we could change the offending build script (or, it was missed). Not sure where the user test PR thingy lives.

(Pinning back and removing the odd import is good too.)

I pinged @orta on that PR, but I'll mention him here too. Do we want to depend on import() for chalk or just pin it to ^4.2.1?

Pinning to 4.2 is fine IMO 👍🏻 - both solve the underlaying issue.

Makes sense that this would break on older nodes which don't support node's import infra. If this is forcing an update to the build infra then we can ship it independently later once that's sorted.

I've reverted the changes in #46931 as well.

@typescript-bot cherry-pick this to release-4.5

Heya @andrewbranch, I've started to run the task to cherry-pick this into release-4.5 on this PR at e1b49bb. You can monitor the build here.

I think this doesn't work after the branch has been deleted but we'll see

Hey @andrewbranch, I couldn't open a PR with the cherry-pick. (You can check the log here). You may need to squash and pick this PR into release-4.5 manually.