WSL v1-npm在安装grpc时崩溃

我正在使用WSLV.1，我正在尝试在本地启动基于React的前端bazaar应用程序。因此，我基本上键入了

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

，但错误一直在闪烁。我甚至安装了带有

-g

选项的

grpc

，以进行全局安装，但在此之后运行

npm install

时，它再次崩溃

---

有没有人经历过这种情况，或者知道如何解决它？

这是WSL v1中最古老的错误之一的一个实例，影响了许多不同的npm包：。我还使用WSL进行开发，并通过切换到WSL v2解决了这个问题