Closed Blond11516 closed 7 months ago
Turns out we didn't even use glob
(nor ts-node
for that matter) so the migration wasn't strictly necessary. That said I still think it's worth it because it lets us use a package manager that is actively maintained and should offer better compatibility with the JS ecosystem moving forward.
While I usually find yarn a little easier to use,
@vscode/vsce
only supports yarn version 1, which does not properly handle theengines
field frompackage.json
. This in turn causes a test failure with the latest version ofglob
. I don't think being blocked on a depedency upgrade (and potentially others in the future) is worth sticking with yarn.