WSL v1 - npm 在安装 grpc 时崩溃

WSL v1 - npm crashes at installing grpc

我正在使用 WSL v.1,我正在尝试在本地启动 DataTurks' 基于 React 的前端集市应用程序。所以我基本上输入 npm install 但是当 npm 到达库 grpc 并且提供的错误是:

时我 运行 出错了
path /home/kmartin62/DataTurks/bazaar/node_modules/.staging/grpc-2c7a1feb/node_modules/mkdirp
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall rename
npm ERR! Error: EACCES: permission denied, rename '/home/kmartin62/DataTurks/bazaar/node_modules/.staging/grpc-2c7a1feb/node_modules/mkdirp' -> '/home/kmartin62/DataTurks/bazaar/node_modules/.staging/mkdirp-97188a16'
npm ERR!  { Error: EACCES: permission denied, rename '/home/kmartin62/DataTurks/bazaar/node_modules/.staging/grpc-2c7a1feb/node_modules/mkdirp' -> '/home/kmartin62/DataTurks/bazaar/node_modules/.staging/mkdirp-97188a16'
npm ERR!   cause:
npm ERR!    { Error: EACCES: permission denied, rename '/home/kmartin62/DataTurks/bazaar/node_modules/.staging/grpc-2c7a1feb/node_modules/mkdirp' -> '/home/kmartin62/DataTurks/bazaar/node_modules/.staging/mkdirp-97188a16'
npm ERR!      errno: -13,
npm ERR!      code: 'EACCES',
npm ERR!      syscall: 'rename',
npm ERR!      path: '/home/kmartin62/DataTurks/bazaar/node_modules/.staging/grpc-2c7a1feb/node_modules/mkdirp',
npm ERR!      dest: '/home/kmartin62/DataTurks/bazaar/node_modules/.staging/mkdirp-97188a16' },
npm ERR!   stack: 'Error: EACCES: permission denied, rename \'/home/kmartin62/DataTurks/bazaar/node_modules/.staging/grpc-2c7a1feb/node_modules/mkdirp\' -> \'/home/kmartin62/DataTurks/bazaar/node_modules/.staging/mkdirp-97188a16\'',
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'rename',
npm ERR!   path: '/home/kmartin62/DataTurks/bazaar/node_modules/.staging/grpc-2c7a1feb/node_modules/mkdirp',
npm ERR!   dest: '/home/kmartin62/DataTurks/bazaar/node_modules/.staging/mkdirp-97188a16',
npm ERR!   parent: '@firebase/firestore' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

我试图以超级用户身份安装它,sudo但错误一直闪烁。我什至安装了 grpc-g 选项,用于全局安装,但是当我 运行 npm install 之后它再次崩溃。

有没有人遇到过这个问题或者有人知道如何解决这个问题?

这是 WSL v1 中最古老的错误之一的实例,影响了许多不同的 npm 包:https://github.com/microsoft/WSL/issues/14。我也使用 WSL 进行开发,我通过切换到 WSL v2 解决了这个问题。