build: upgrade to npm@latest or yarn@latest

[jaketrent]

I would prefer npm to yarn.

Because:

• Comes with node install. Not a separate lib
• Applicable feature set is mutually similar with yarn (npm@latest includes workspaces)

Either way, running into this problem on yarn@1.22:

yarnpkg/yarn#7807

yarn install

=> error An unexpected error occurred: "expected workspace package to exist for \"babel-loader\"".
info If you think this is a bug, please open a bug report with the information provided in "/Users/jaketrent/dev/design-system/packages/icon/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
error Command failed.
Exit code: 1

Also getting this for yarn add commands in packages.

Solved it with reverting to yarn@1.18:

yarnpkg/yarn#7807 (comment)

yarn policies set-version 1.18.0

Feeling like yarn@1.x is dead: yarnpkg/yarn#7734 (comment)

[jaketrent]

Team triage: use npm@latest.

In the meantime, another potential workaround: https://github.com/lerna/lerna/tree/main/commands/add#readme

GitHub

lerna/lerna

🐉 A tool for managing JavaScript projects with multiple packages. - lerna/lerna

[EdwardIrby]

Need to document this in #1968 in transition internal best pracices

[caseybaggz]

NPM latest causes break in the build and testing environment. Yarn cannot be upgraded to latest because Lerna and Gatsby do not support Yarn 2+. 😞