Error on running npm install on root folder

OS: windows 10
node : v12.18.2
npm : 6.14.8
windows-build-tools: -- windows-build-tools@5.2.2
I have installed all the required dependencies. I have also read all the similar issues and the BUILD.md

Output:

user@DESKTOP-L3PC93N MINGW64 ~/Desktop/joplin (dev)
$ npm install

root@ postinstall C:\Users\user\Desktop\joplin
npm run bootstrap --no-ci && npm run build

root@ bootstrap C:\Users\user\Desktop\joplin
lerna bootstrap --force-local --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 1 in '@joplin/renderer'
lerna ERR! npm install stderr:
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\getpass-4c5f3536\package.json'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\getpass-4c5f3536.npmignore'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\get-value-04b37a99\package.json'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\get-package-type-37eeedb6\LICENSE'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\get-caller-file-d4ee19f5\package.json'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\function-bind-10fd3536\package.json'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\getpass-4c5f3536\README.md'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\get-value-04b37a99\LICENSE'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\get-package-type-37eeedb6\async.cjs'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\get-caller-file-d4ee19f5\index.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\function-bind-10fd3536.npmignore'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\getpass-4c5f3536\LICENSE'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\get-value-04b37a99\index.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\get-package-type-37eeedb6\cache.cjs'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\get-caller-file-d4ee19f5\index.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\function-bind-10fd3536\README.md'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\gensync-6a0200d6\test.babelrc'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\has-a3687026\src\index.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\growly-9e81ae6b\example\bakery.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\node-notifier-5d248bb8\lib\checkGrowl.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\lodash-c5a51f0c\fp\xorBy.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\lodash-c5a51f0c\fp\xorWith.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\lodash-c5a51f0c\fp\zip.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\lodash-c5a51f0c\fp\zipAll.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\lodash-c5a51f0c\fp\zipObj.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\lodash-c5a51f0c\fp\zipObject.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\lodash-c5a51f0c\fp\zipObjectDeep.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\user\Desktop\joplin\packages\renderer\node_modules.staging\lodash-c5a51f0c\fp\zipWith.js'

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Roaming\npm-cache_logs\2021-07-26T13_09_37_256Z-debug.log

lerna ERR! npm install exited 1 in '@joplin/renderer'
lerna WARN complete Waiting for 5 child processes to exit. CTRL-C to exit immediately.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! root@ bootstrap: lerna bootstrap --force-local --no-ci
npm ERR! Exit status 1
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\user\AppData\Roaming\npm-cache_logs\2021-07-26T13_09_41_980Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! root@ postinstall: npm run bootstrap --no-ci && npm run build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the root@ 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\user\AppData\Roaming\npm-cache_logs\2021-07-26T13_09_42_170Z-debug.log

The actual output is way big. I have removed the middle part of the error. I have tried deleting the folder and again downloading it. I have tried multiple ways to solve it but didn't work.

Windows generally doesn't work well with Node and npm, so maybe try WSL (which is very slow but works a bit better). If you want to try from Windows, make sure to close any text editor that might have a file open in the source directory, as often it's a problem with locked files.

I tried running npm install --force. I got some output but I am not sure whether it is correct or not.
This is the last few lines of the output

@joplin/lib: npm WARN using --force I sure hope you know what you are doing.
joplin: > joplin@2.2.0 tsc C:\Users\user\Desktop\test\joplin\packages\app-cli
joplin: > node node_modules/typescript/bin/tsc --project tsconfig.json
@joplin/plugin-repo-cli: npm WARN using --force I sure hope you know what you are doing.
@joplin/renderer: npm WARN using --force I sure hope you know what you are doing.
@joplin/app-desktop: > @joplin/app-desktop@2.2.2 tsc C:\Users\user\Desktop\test\joplin\packages\app-desktop
@joplin/app-desktop: > node node_modules/typescript/bin/tsc --project tsconfig.json
@joplin/server: npm WARN using --force I sure hope you know what you are doing.
@joplin/lib: > @joplin/lib@2.2.0 tsc C:\Users\user\Desktop\test\joplin\packages\lib
@joplin/lib: > node node_modules/typescript/bin/tsc --project tsconfig.json
@joplin/plugin-repo-cli: > @joplin/plugin-repo-cli@2.2.0 tsc C:\Users\user\Desktop\test\joplin\packages\plugin-repo-cli
@joplin/plugin-repo-cli: > tsc --project tsconfig.json
@joplin/tools: npm WARN using --force I sure hope you know what you are doing.
@joplin/renderer: > @joplin/renderer@2.2.0 tsc C:\Users\user\Desktop\test\joplin\packages\renderer
@joplin/renderer: > node node_modules/typescript/bin/tsc --project tsconfig.json
@joplin/server: > @joplin/server@2.2.8 tsc C:\Users\user\Desktop\test\joplin\packages\server
@joplin/server: > tsc --project tsconfig.json
@joplin/tools: > @joplin/tools@2.2.0 tsc C:\Users\user\Desktop\test\joplin\packages\tools
@joplin/tools: > tsc --project tsconfig.json
@joplin/app-mobile: npm WARN using --force I sure hope you know what you are doing.
@joplin/app-mobile: > @joplin/app-mobile@0.8.9 tsc C:\Users\user\Desktop\test\joplin\packages\app-mobile
@joplin/app-mobile: > node node_modules/typescript/bin/tsc --project tsconfig.json
lerna success run Ran npm script 'tsc' in 8 packages in 35.4s:
lerna success - joplin
lerna success - @joplin/app-desktop
lerna success - @joplin/app-mobile
lerna success - @joplin/lib
lerna success - @joplin/plugin-repo-cli
lerna success - @joplin/renderer
lerna success - @joplin/server
lerna success - @joplin/tools
npm WARN @octokit/plugin-request-log@1.0.2 requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-plugin-react-hooks@2.5.1 requires a peer of eslint@^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 but none is installed. You must install peer dependencies yourself.

added 5 packages from 13 contributors and audited 1591 packages in 271.855s

90 packages are looking for funding
run npm fund for details

found 63 vulnerabilities (44 moderate, 19 high)
run npm audit fix to fix them, or npm audit for details

There are no errors there as far as I can see

This is my first time with open source.. Sorry if you are finding my doubts silly. It is just that I would love to contribute to this project

Since the output after running the --force command was big I didn't include the entire output in my previous reply. I just wanted to make sure whether running --force command is harmful or not.

This is the output which I got after running npm install --force.
Is it fine or should I go for wsl. I downloaded the wsl 2 in my system. .

--------------------------------- Output ---------------

C:\Users\user\Desktop\joplin>npm install --force
npm WARN using --force I sure hope you know what you are doing.

fsevents@1.2.13 install C:\Users\user\Desktop\joplin\node_modules\fsevents
node install.js

Skipping 'fsevents' build as platform win32 is not supported

root@ postinstall C:\Users\user\Desktop\joplin
npm run bootstrap --no-ci && npm run build

npm WARN using --force I sure hope you know what you are doing.
npm WARN using --force I sure hope you know what you are doing.

root@ bootstrap C:\Users\user\Desktop\joplin
lerna bootstrap --force-local --no-ci

lerna notice cli v3.22.1
lerna info versioning independent
lerna info Bootstrapping 15 packages
lerna info Installing external dependencies
lerna info Symlinking packages and binaries
lerna info lifecycle @joplin/app-clipper@1.0.8~postinstall: @joplin/app-clipper@1.0.8
lerna info lifecycle @joplin/app-desktop@2.2.2~postinstall: @joplin/app-desktop@2.2.2
lerna info lifecycle @joplin/app-mobile@0.8.9~postinstall: @joplin/app-mobile@0.8.9

@joplin/app-desktop@2.2.2 postinstall C:\Users\user\Desktop\joplin\packages\app-desktop
npm run build

npm WARN using --force I sure hope you know what you are doing.
npm WARN using --force I sure hope you know what you are doing.

@joplin/app-desktop@2.2.2 build C:\Users\user\Desktop\joplin\packages\app-desktop
gulp build

C:/Users/user/Desktop/joplin
[01:17:27] Using gulpfile ~\Desktop\joplin\packages\app-desktop\gulpfile.js
[01:17:27] Starting 'build'...
[01:17:27] Starting 'compileScripts'...
[01:17:27] Starting 'compilePackageInfo'...
[01:17:27] Starting 'copyPluginAssets'...
[01:17:27] Starting 'copyTinyMceLangs'...
[01:17:27] Starting 'updateIgnoredTypeScriptBuild'...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/ClipperConfigScreen.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/EncryptionConfigScreen.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/ExtensionBadge.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/HelpButton.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/IconButton.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/ImportScreen.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/ItemList.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/Navigator.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/NotePropertiesDialog.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/NoteRevisionViewer.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/NoteSearchBar.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/NoteStatusBar.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/PromptDialog.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/TagItem.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/ToolbarSpace.jsx...
Compiling C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/VerticalResizer.jsx...
Copying to C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/note-viewer/pluginAssets
Copying C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../../../Assets/TinyMCE/langs => C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../node_modules/tinymce/langs
[01:17:39] Finished 'compileScripts' after 12 s
[01:17:39] Finished 'compilePackageInfo' after 12 s
[01:17:39] Finished 'updateIgnoredTypeScriptBuild' after 12 s
Copying to C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../pluginAssets
[01:17:39] Finished 'copyTinyMceLangs' after 12 s
[01:17:39] Finished 'copyPluginAssets' after 12 s
[01:17:39] Finished 'build' after 12 s

@joplin/app-clipper@1.0.8 postinstall C:\Users\user\Desktop\joplin\packages\app-clipper
cd popup && npm install

npm WARN using --force I sure hope you know what you are doing.
npm WARN using --force I sure hope you know what you are doing.

fsevents@1.2.11 install C:\Users\user\Desktop\joplin\packages\app-clipper\popup\node_modules\jest-haste-map\node_modules\fsevents
node-gyp rebuild

C:\Users\user\Desktop\joplin\packages\app-clipper\popup\node_modules\jest-haste-map\node_modules\fsevents>if not defined npm_config_node_gyp (node "C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
gyp ERR! find VS
gyp ERR! find VS msvs_version was set from command line or npm config
gyp ERR! find VS - looking for Visual Studio version 2015
gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
gyp ERR! find VS checking VS2017 (15.9.28307.1585) found at:
gyp ERR! find VS "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools"
gyp ERR! find VS - found "Visual Studio C++ core features"
gyp ERR! find VS - found VC++ toolset: v141
gyp ERR! find VS - found Windows SDK: 10.0.17763.0
gyp ERR! find VS - msvs_version does not match this version
gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS
gyp ERR! find VS valid versions for msvs_version:
gyp ERR! find VS - "2017"
gyp ERR! find VS - "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools"
gyp ERR! find VS
gyp ERR! find VS **************************************************************
gyp ERR! find VS You need to install the latest version of Visual Studio
gyp ERR! find VS including the "Desktop development with C++" workload.
gyp ERR! find VS For more information consult the documentation at:
gyp ERR! find VS GitHub - nodejs/node-gyp: Node.js native addon build tool
gyp ERR! find VS **************************************************************
gyp ERR! find VS
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Visual Studio installation to use
gyp ERR! stack at VisualStudioFinder.fail (C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:121:47)
gyp ERR! stack at C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:74:16
gyp ERR! stack at VisualStudioFinder.findVisualStudio2013 (C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:351:14)
gyp ERR! stack at C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:70:14
gyp ERR! stack at C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:372:16
gyp ERR! stack at C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\util.js:54:7
gyp ERR! stack at C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\util.js:33:16
gyp ERR! stack at ChildProcess.exithandler (child_process.js:310:5)
gyp ERR! stack at ChildProcess.emit (events.js:315:20)
gyp ERR! stack at maybeClose (internal/child_process.js:1021:16)
gyp ERR! System Windows_NT 10.0.19042
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\user\Desktop\joplin\packages\app-clipper\popup\node_modules\jest-haste-map\node_modules\fsevents
gyp ERR! node -v v12.18.2
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok

fsevents@1.2.12 install C:\Users\user\Desktop\joplin\packages\app-clipper\popup\node_modules\react-scripts\node_modules\chokidar\node_modules\fsevents
node-gyp rebuild

C:\Users\user\Desktop\joplin\packages\app-clipper\popup\node_modules\react-scripts\node_modules\chokidar\node_modules\fsevents>if not defined npm_config_node_gyp (node "C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
gyp ERR! find VS
gyp ERR! find VS msvs_version was set from command line or npm config
gyp ERR! find VS - looking for Visual Studio version 2015
gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
gyp ERR! find VS checking VS2017 (15.9.28307.1585) found at:
gyp ERR! find VS "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools"
gyp ERR! find VS - found "Visual Studio C++ core features"
gyp ERR! find VS - found VC++ toolset: v141
gyp ERR! find VS - found Windows SDK: 10.0.17763.0
gyp ERR! find VS - msvs_version does not match this version
gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS
gyp ERR! find VS valid versions for msvs_version:
gyp ERR! find VS - "2017"
gyp ERR! find VS - "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools"
gyp ERR! find VS
gyp ERR! find VS **************************************************************
gyp ERR! find VS You need to install the latest version of Visual Studio
gyp ERR! find VS including the "Desktop development with C++" workload.
gyp ERR! find VS For more information consult the documentation at:
gyp ERR! find VS GitHub - nodejs/node-gyp: Node.js native addon build tool
gyp ERR! find VS **************************************************************
gyp ERR! find VS
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Visual Studio installation to use
gyp ERR! stack at VisualStudioFinder.fail (C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:121:47)
gyp ERR! stack at C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:74:16
gyp ERR! stack at VisualStudioFinder.findVisualStudio2013 (C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:351:14)
gyp ERR! stack at C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:70:14
gyp ERR! stack at C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:372:16
gyp ERR! stack at C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\util.js:54:7
gyp ERR! stack at C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\util.js:33:16
gyp ERR! stack at ChildProcess.exithandler (child_process.js:310:5)
gyp ERR! stack at ChildProcess.emit (events.js:315:20)
gyp ERR! stack at maybeClose (internal/child_process.js:1021:16)
gyp ERR! System Windows_NT 10.0.19042
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\user\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\user\Desktop\joplin\packages\app-clipper\popup\node_modules\react-scripts\node_modules\chokidar\node_modules\fsevents
gyp ERR! node -v v12.18.2
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok

fsevents@1.2.13 install C:\Users\user\Desktop\joplin\packages\app-clipper\popup\node_modules\watchpack-chokidar2\node_modules\fsevents
node install.js

Skipping 'fsevents' build as platform win32 is not supported

fsevents@1.2.13 install C:\Users\user\Desktop\joplin\packages\app-clipper\popup\node_modules\webpack-dev-server\node_modules\fsevents
node install.js

Skipping 'fsevents' build as platform win32 is not supported

core-js@2.6.11 postinstall C:\Users\user\Desktop\joplin\packages\app-clipper\popup\node_modules\babel-runtime\node_modules\core-js
node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( GitHub - zloirock/core-js: Standard Library ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:

https://opencollective.com/core-js
Denis Pushkarev is creating core-js | Patreon

Also, the author of core-js ( zloirock (Denis Pushkarev) · GitHub ) is looking for a good job -)

core-js@3.6.4 postinstall C:\Users\user\Desktop\joplin\packages\app-clipper\popup\node_modules\core-js
node -e "try{require('./postinstall')}catch(e){}"

core-js-pure@3.6.5 postinstall C:\Users\user\Desktop\joplin\packages\app-clipper\popup\node_modules\core-js-pure
node -e "try{require('./postinstall')}catch(e){}"

joplin-webclipper-popup@0.1.0 postinstall C:\Users\user\Desktop\joplin\packages\app-clipper\popup
node postinstall.js && npm run build

npm WARN using --force I sure hope you know what you are doing.
npm WARN using --force I sure hope you know what you are doing.

joplin-webclipper-popup@0.1.0 build C:\Users\user\Desktop\joplin\packages\app-clipper\popup
node scripts/build.js SKIP_PREFLIGHT_CHECK

Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run the following command: npm update
Compiled successfully.

File sizes after gzip:

47.92 KB build\static\js\2.chunk.js
8.53 KB build\static\js\main.chunk.js
775 B build\static\js\runtime-main.js
771 B build\static\css\main.chunk.css

The project was built assuming it is hosted at ./.
You can control this with the homepage field in your package.json.

The build folder is ready to be deployed.

Find out more about deployment here:

bit.ly/CRA-deploy

npm WARN The package fs-extra is included as both a dev and production dependency.

added 2044 packages from 817 contributors and audited 2048 packages in 105.81s

68 packages are looking for funding
run npm fund for details

found 1045 vulnerabilities (786 low, 243 moderate, 16 high)
run npm audit fix to fix them, or npm audit for details

@joplin/app-mobile@0.8.9 postinstall C:\Users\user\Desktop\joplin\packages\app-mobile
jetify && npm run build

Jetifier found 1288 file(s) to forward-jetify. Using 8 workers...
npm WARN using --force I sure hope you know what you are doing.
npm WARN using --force I sure hope you know what you are doing.

@joplin/app-mobile@0.8.9 build C:\Users\user\Desktop\joplin\packages\app-mobile
gulp build

[01:19:52] Using gulpfile ~\Desktop\joplin\packages\app-mobile\gulpfile.js
[01:19:52] Starting 'build'...
[01:19:52] Starting 'buildInjectedJs'...
Building CodeMirror bundle...
Creating: C:\Users\user\Desktop\joplin/packages/app-mobile/lib/rnInjectedJs/webviewLib.js
Creating: C:\Users\user\Desktop\joplin/packages/app-mobile/lib/rnInjectedJs/CodeMirror.bundle.js
[01:20:05] Finished 'buildInjectedJs' after 13 s
[01:20:05] Starting 'encodeAssets'...
[01:20:05] Finished 'encodeAssets' after 279 ms
[01:20:05] Starting 'podInstall'...
[01:20:05] Finished 'podInstall' after 719 μs
[01:20:05] Finished 'build' after 13 s
lerna info lifecycle @joplin/fork-htmlparser2@4.1.28~prepare: @joplin/fork-htmlparser2@4.1.28
lerna info lifecycle @joplin/turndown-plugin-gfm@1.0.32~prepare: @joplin/turndown-plugin-gfm@1.0.32
lerna info lifecycle @joplin/turndown@4.0.50~prepare: @joplin/turndown@4.0.50

@joplin/fork-htmlparser2@4.1.28 prepare C:\Users\user\Desktop\joplin\packages\fork-htmlparser2
npm run build

npm WARN using --force I sure hope you know what you are doing.
npm WARN using --force I sure hope you know what you are doing.

@joplin/fork-htmlparser2@4.1.28 build C:\Users\user\Desktop\joplin\packages\fork-htmlparser2
tsc

@joplin/turndown-plugin-gfm@1.0.32 prepare C:\Users\user\Desktop\joplin\packages\turndown-plugin-gfm
npm run build

npm WARN using --force I sure hope you know what you are doing.
npm WARN using --force I sure hope you know what you are doing.

@joplin/turndown-plugin-gfm@1.0.32 build C:\Users\user\Desktop\joplin\packages\turndown-plugin-gfm
rollup -c config/rollup.config.cjs.js

src/gfm.js → lib/turndown-plugin-gfm.cjs.js...
created lib/turndown-plugin-gfm.cjs.js in 59ms

@joplin/turndown@4.0.50 prepare C:\Users\user\Desktop\joplin\packages\turndown
npm run build

npm WARN using --force I sure hope you know what you are doing.
npm WARN using --force I sure hope you know what you are doing.

@joplin/turndown@4.0.50 build C:\Users\user\Desktop\joplin\packages\turndown
rollup -c config/rollup.config.cjs.js

src/turndown.js → lib/turndown.cjs.js...
created lib/turndown.cjs.js in 242ms
lerna success Bootstrapped 15 packages
npm WARN using --force I sure hope you know what you are doing.
npm WARN using --force I sure hope you know what you are doing.

root@ build C:\Users\user\Desktop\joplin
lerna run build && npm run tsc

lerna notice cli v3.22.1
lerna info versioning independent
lerna info Executing command in 6 packages: "npm run build"
lerna info run Ran npm script 'build' in '@joplin/turndown-plugin-gfm' in 2.2s:

@joplin/turndown-plugin-gfm@1.0.32 build C:\Users\user\Desktop\joplin\packages\turndown-plugin-gfm
rollup -c config/rollup.config.cjs.js

lerna info run Ran npm script 'build' in '@joplin/turndown' in 5.5s:

@joplin/turndown@4.0.50 build C:\Users\user\Desktop\joplin\packages\turndown
rollup -c config/rollup.config.cjs.js

lerna info run Ran npm script 'build' in 'joplin' in 7.5s:

joplin@2.2.0 build C:\Users\user\Desktop\joplin\packages\app-cli
gulp build

[01:20:27] Using gulpfile ~\Desktop\joplin\packages\app-cli\gulpfile.js
[01:20:27] Starting 'build'...
[01:20:27] Starting 'prepareBuild'...
[01:20:27] Finished 'prepareBuild' after 376 ms
[01:20:27] Finished 'build' after 379 ms
lerna info run Ran npm script 'build' in '@joplin/app-desktop' in 8.9s:

@joplin/app-desktop@2.2.2 build C:\Users\user\Desktop\joplin\packages\app-desktop
gulp build

C:/Users/user/Desktop/joplin
[01:20:26] Using gulpfile ~\Desktop\joplin\packages\app-desktop\gulpfile.js
[01:20:26] Starting 'build'...
[01:20:26] Starting 'compileScripts'...
[01:20:26] Starting 'compilePackageInfo'...
[01:20:26] Starting 'copyPluginAssets'...
[01:20:26] Starting 'copyTinyMceLangs'...
[01:20:26] Starting 'updateIgnoredTypeScriptBuild'...
Copying to C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../gui/note-viewer/pluginAssets
Copying C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../../../Assets/TinyMCE/langs => C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../node_modules/tinymce/langs
[01:20:28] Finished 'compileScripts' after 1.96 s
[01:20:28] Finished 'compilePackageInfo' after 1.96 s
[01:20:28] Finished 'updateIgnoredTypeScriptBuild' after 1.99 s
[01:20:28] Finished 'copyTinyMceLangs' after 2.03 s
Copying to C:\Users\user\Desktop\joplin\packages\app-desktop\tools/../pluginAssets
[01:20:28] Finished 'copyPluginAssets' after 2.1 s
[01:20:28] Finished 'build' after 2.1 s
lerna info run Ran npm script 'build' in '@joplin/fork-htmlparser2' in 10.9s:

@joplin/fork-htmlparser2@4.1.28 build C:\Users\user\Desktop\joplin\packages\fork-htmlparser2
tsc

lerna info run Ran npm script 'build' in '@joplin/app-mobile' in 19.1s:

@joplin/app-mobile@0.8.9 build C:\Users\user\Desktop\joplin\packages\app-mobile
gulp build

[01:20:23] Using gulpfile ~\Desktop\joplin\packages\app-mobile\gulpfile.js
[01:20:23] Starting 'build'...
[01:20:23] Starting 'buildInjectedJs'...
Building CodeMirror bundle...
Creating: C:\Users\user\Desktop\joplin/packages/app-mobile/lib/rnInjectedJs/webviewLib.js
Creating: C:\Users\user\Desktop\joplin/packages/app-mobile/lib/rnInjectedJs/CodeMirror.bundle.js
[01:20:38] Finished 'buildInjectedJs' after 16 s
[01:20:38] Starting 'encodeAssets'...
[01:20:39] Finished 'encodeAssets' after 234 ms
[01:20:39] Starting 'podInstall'...
[01:20:39] Finished 'podInstall' after 394 μs
[01:20:39] Finished 'build' after 16 s
lerna success run Ran npm script 'build' in 6 packages in 19.2s:
lerna success - joplin
lerna success - @joplin/app-desktop
lerna success - @joplin/app-mobile
lerna success - @joplin/fork-htmlparser2
lerna success - @joplin/turndown-plugin-gfm
lerna success - @joplin/turndown
npm WARN using --force I sure hope you know what you are doing.
npm WARN using --force I sure hope you know what you are doing.

root@ tsc C:\Users\user\Desktop\joplin
lerna run tsc --stream --parallel

lerna notice cli v3.22.1
lerna info versioning independent
lerna info Executing command in 8 packages: "npm run tsc"
joplin: npm WARN using --force I sure hope you know what you are doing.
@joplin/app-desktop: npm WARN using --force I sure hope you know what you are doing.
@joplin/app-mobile: npm WARN using --force I sure hope you know what you are doing.
@joplin/lib: npm WARN using --force I sure hope you know what you are doing.
@joplin/plugin-repo-cli: npm WARN using --force I sure hope you know what you are doing.
@joplin/renderer: npm WARN using --force I sure hope you know what you are doing.
@joplin/server: npm WARN using --force I sure hope you know what you are doing.
@joplin/tools: npm WARN using --force I sure hope you know what you are doing.
joplin: npm WARN using --force I sure hope you know what you are doing.
@joplin/app-mobile: npm WARN using --force I sure hope you know what you are doing.
@joplin/app-desktop: npm WARN using --force I sure hope you know what you are doing.
@joplin/lib: npm WARN using --force I sure hope you know what you are doing.
joplin: > joplin@2.2.0 tsc C:\Users\user\Desktop\joplin\packages\app-cli
joplin: > node node_modules/typescript/bin/tsc --project tsconfig.json
@joplin/app-mobile: > @joplin/app-mobile@0.8.9 tsc C:\Users\user\Desktop\joplin\packages\app-mobile
@joplin/app-mobile: > node node_modules/typescript/bin/tsc --project tsconfig.json
@joplin/plugin-repo-cli: npm WARN using --force I sure hope you know what you are doing.
@joplin/renderer: npm WARN using --force I sure hope you know what you are doing.
@joplin/app-desktop: > @joplin/app-desktop@2.2.2 tsc C:\Users\user\Desktop\joplin\packages\app-desktop
@joplin/app-desktop: > node node_modules/typescript/bin/tsc --project tsconfig.json
@joplin/lib: > @joplin/lib@2.2.0 tsc C:\Users\user\Desktop\joplin\packages\lib
@joplin/lib: > node node_modules/typescript/bin/tsc --project tsconfig.json
@joplin/tools: npm WARN using --force I sure hope you know what you are doing.
@joplin/server: npm WARN using --force I sure hope you know what you are doing.
@joplin/plugin-repo-cli: > @joplin/plugin-repo-cli@2.2.0 tsc C:\Users\user\Desktop\joplin\packages\plugin-repo-cli
@joplin/plugin-repo-cli: > tsc --project tsconfig.json
@joplin/renderer: > @joplin/renderer@2.2.0 tsc C:\Users\user\Desktop\joplin\packages\renderer
@joplin/renderer: > node node_modules/typescript/bin/tsc --project tsconfig.json
@joplin/tools: > @joplin/tools@2.2.0 tsc C:\Users\user\Desktop\joplin\packages\tools
@joplin/tools: > tsc --project tsconfig.json
@joplin/server: > @joplin/server@2.2.8 tsc C:\Users\user\Desktop\joplin\packages\server
@joplin/server: > tsc --project tsconfig.json
lerna success run Ran npm script 'tsc' in 8 packages in 28.9s:
lerna success - joplin
lerna success - @joplin/app-desktop
lerna success - @joplin/app-mobile
lerna success - @joplin/lib
lerna success - @joplin/plugin-repo-cli
lerna success - @joplin/renderer
lerna success - @joplin/server
lerna success - @joplin/tools
npm WARN @octokit/plugin-request-log@1.0.2 requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-plugin-react-hooks@2.5.1 requires a peer of eslint@^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 but none is installed. You must install peer dependencies yourself.

added 5 packages from 13 contributors and audited 1591 packages in 257.262s

90 packages are looking for funding
run npm fund for details

found 63 vulnerabilities (44 moderate, 19 high)
run npm audit fix to fix them, or npm audit for details

Ok, now I see the error.
In future when posting logs or code wrap them in 3 backticks ``` that'd make it more readable.

Did you install windows-build-tools like it's said the BUILD.md doc?

npm install -g windows-build-tools --vs2015

If not - give it a try.

Even though I had installed the vs2015 of windows-build-tools. I tried installing it once again. Surprisingly it worked now. I am not sure why it was not working previously. But thank you for all the help. Surely I would love to contribute to this project.

The command does not always work. It does something but does not install the 2015 version.
I've been messing around with one of my windows installations with this problem. You can also find in the repro some issues to the problem.

I installed it myself by hand in the end.

Windows Build Tools 2015

Invoke-WebRequest -Uri https://download.microsoft.com/download/5/f/7/5f7acaeb-8363-451f-9425-68a90f98b238/visualcppbuildtools_full.exe -OutFile visualcppbuildtools_full.exe
visualcppbuildtools_full.exe /NoRestart /S /L
[Environment]::SetEnvironmentVariable("GYP_MSVS_VERSION", "2015", "User")
npm config set msvs_version 2015

Another option is to install the 2017 with the option Microsoft.VisualStudio.Workload.VCTools.

I can test the whole thing again on a new installation and update documentation or add some infos?

Yeah, I saw that too. That thing is a mess.

I am not sure what's the problem with windows-build-tools. When I run npm install with --force parameter it works. It doesn't give any error. But if I try without the force parameter it gives me the gyp-node error