feat: use pnpm instead npm

[await-ovo]

Summary

The main advantages of using pnpm are:

• save local disk space

• improve installation speed

• avoid the problem that the first npm run build of a newly cloned repository has a high probability of error(It often occurs in our ci process):

    ✖  @svgr/plugin-jsx:build
       > @svgr/plugin-jsx@7.0.0 build
       > rollup -c ../../build/rollup.config.mjs


       src/index.ts → ./dist/index.js...
       created ./dist/index.js in 84ms

       src/index.ts → ./dist/index.d.ts...
       src/index.ts(7,37): error TS2307: Cannot find module '@svgr/core' or its corresponding type declarations.
       src/index.ts(38,28): error TS7006: Parameter 'code' implicitly has an 'any' type.
       src/index.ts(38,34): error TS7006: Parameter 'config' implicitly has an 'any' type.
       src/index.ts(38,42): error TS7006: Parameter 'state' implicitly has an 'any' type.

       [!] (plugin dts) RollupError: Failed to compile. Check the logs above.

• avoid phantom dependency

Test plan

• After pnpm install, the build and test both succeed.
• vercel dev run success and in api directory after pnpm install.
• publish packages using lerna, refer to the documentation here

I need help to verify that the release is working properly

Because netlify always fails for some reason when deployed (local is fine), Keep the website still using npm.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
svgr	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 7, 2023 1:01pm

[codecov]

Codecov Report

Merging #852 (d14751b) into main (649fa65) will not change coverage.
The diff coverage is n/a.

❗ Current head d14751b differs from pull request most recent head d32f583. Consider uploading reports for the commit d32f583 to get more accurate results

@@           Coverage Diff           @@
##             main     #852   +/-   ##
=======================================
  Coverage   92.80%   92.80%           
=======================================
  Files          32       32           
  Lines         751      751           
  Branches      249      249           
=======================================
  Hits          697      697           
  Misses         53       53           
  Partials        1        1           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[gregberge]

@await-ovo very good thank you! Could you try to run lerna? You will be blocked on npm but everything else should work right?

[await-ovo]

@await-ovo very good thank you! Could you try to run lerna? You will be blocked on npm but everything else should work right?

Because I'm not familiar with lerna, do I need to run pnpm lerna version first and then pnpm run release, I've been doing this locally and it gives me an error every time:

$ pnpm release --dry-run

> @ release /Users/Documents/projects/svgr
> lerna publish --conventional-commits && conventional-github-releaser --preset angular "--dry-run"

lerna notice cli v6.6.0
lerna info current version 7.0.2
lerna notice Current HEAD is already released, skipping change detection.
lerna success No changed packages to publish 
/Users/Documents/projects/svgr/node_modules/.pnpm/minimist-options@4.1.0/node_modules/minimist-options/index.js:101
                                        throw new TypeError(`Expected "${key}" default value to be of type "${expectedType}", got ${prettyPrint(defaultType)}`);
                                        ^

TypeError: Expected "token" default value to be of type "string", got "undefined"

[await-ovo]

I think we should verify that the workspace protocol is replaced with the specific version when the package is released.

[gregberge]

@await-ovo I think I will merge and try to make a release. Thanks!