Still the error persists. Output is as follows:
PS D:\GSOC\joplin> npm cache verify
Cache verified and compressed (~\AppData\Roaming\npm-cache\_cacache):
Content verified: 4839 (422284382 bytes)
Content garbage-collected: 2 (3946385 bytes)
Index entries: 7559
Finished in 7.8s
PS D:\GSOC\joplin> npm ci
npm WARN prepare removing existing node_modules/ before installation
> husky@3.1.0 install D:\GSOC\joplin\node_modules\husky
> node husky install
husky > Setting up git hooks
husky > Done
> husky@3.1.0 postinstall D:\GSOC\joplin\node_modules\husky
> opencollective-postinstall || exit 0
Thank you for using husky!
If you rely on this package, please consider supporting our open collective:
> https://opencollective.com/husky/donate
> fsevents@1.2.13 install D:\GSOC\joplin\node_modules\fsevents
> node install.js
Skipping 'fsevents' build as platform win32 is not supported
> root@undefined postinstall D:\GSOC\joplin
> npm run bootstrap --no-ci && npm run build
> root@ bootstrap D:\GSOC\joplin
> lerna bootstrap --no-ci
lerna notice cli v3.22.1
lerna info versioning independent
lerna info Bootstrapping 15 packages
lerna info Installing external dependencies
lerna ERR! npm install exited 4294963248 in '@joplin/server'
lerna ERR! npm install stderr:
npm ERR! code EPERM
npm ERR! syscall unlink
npm ERR! path D:\GSOC\joplin\packages\server\node_modules\.staging\typescript-9e3316e4\lib\typingsInstaller.js
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, unlink 'D:\GSOC\joplin\packages\server\node_modules\.staging\typescript-9e3316e4\lib\typingsInstaller.js'
npm ERR! [Error: EPERM: operation not permitted, unlink 'D:\GSOC\joplin\packages\server\node_modules\.staging\typescript-9e3316e4\lib\typingsInstaller.js'] {
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'unlink',
npm ERR! path: 'D:\\GSOC\\joplin\\packages\\server\\node_modules\\.staging\\typescript-9e3316e4\\lib\\typingsInstaller.js'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\LSR\AppData\Roaming\npm-cache\_cacache\_logs\2021-03-18T11_23_59_003Z-debug.log
lerna ERR! npm install exited 4294963248 in '@joplin/server'
lerna WARN complete Waiting for 7 child processes to exit. CTRL-C to exit immediately.
npm ERR! code ELIFECYCLE
npm ERR! errno 4294963248
npm ERR! root@ bootstrap: `lerna bootstrap --no-ci`
npm ERR! Exit status 4294963248
npm ERR!
npm ERR! Failed at the root@ bootstrap script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\LSR\AppData\Roaming\npm-cache\_cacache\_logs\2021-03-18T11_24_01_334Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 4294963248
npm ERR! root@undefined postinstall: `npm run bootstrap --no-ci && npm run build`
npm ERR! Exit status 4294963248
npm ERR!
npm ERR! Failed at the root@undefined postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\LSR\AppData\Roaming\npm-cache\_logs\2021-03-18T11_24_01_466Z-debug.log
After forking, I have to clone the project by being on the dev branch right?