build(npm): migrate to npm

[bryanjtc]

Migrates from yarn to npm

[skovy]

I haven't been following the yarn releases, is there a significant benefit to v3? When initially working on this project yarn had many features and nice things npm lacked. However, npm has mostly caught up with the things this project uses. Thoughts on switching to latest npm instead of yarn completely?

[bryanjtc]

The only thing that npm still lacks significantly is speed. It still is slower than yarn. Yarn introduced plug n' play and zero installs with v2. Plug n' play get rids of node_modules and zero installs just commits the cache folder. This pr doesn't implement plug n' play or zero installs. I can add it in another pr. V3 improves performance and compability. Ideally when you run yarn install with plug n' play and zero installs, the install time is 0 or a few seconds if there is a package that needs to be build like esbuild and sass.

[bryanjtc]

@skovy What are your thoughts? I can still redo the pr to move to npm v9 or pnpm.

[skovy]

my preference would be npm because it's still the "standard" in the community and this project is fairly standard (or would like to keep it so as much as possible)

[bryanjtc]

@skovy done

[skovy]

Apologies for the merge conflicts, Travis has been flakey so I setup GitHub actions, which should be more reliable. That also means the alpha branch should work and we can merge into it.

[bryanjtc]

I changed the base branch to alpha

[github-actions]

🎉 This PR is included in version 7.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀