Error While Setting up

nikhilgupta2001 · 25 February 2021 17:01

using npm install command

laurent · 25 February 2021 17:04

Not posting the complete command that was typed - check ✓
Posting a screenshot instead of the log - check ✓
No version info - check ✓
Not posting the complete log but only the less relevant parts - check ✓

nikhilgupta2001 · 25 February 2021 17:11

$ npm install

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

root@ bootstrap C:\Users\HP PC\Desktop\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 1 in '@joplin/lib'
lerna ERR! npm install stderr:
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\HP PC\Desktop\joplin\packages\lib\node_modules.staging\aws-sdk-000adec5\scripts\lib\extra-2018-08-02.normal.json'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\HP PC\Desktop\joplin\packages\lib\node_modules.staging\aws-sdk-000adec5\scripts\lib\foo-2018-03-30.normal.json'
npm WARN tar ENOENT: no such file or directory, lstat 'C:\Users\HP PC\Desktop\joplin\packages\lib\node_modules.staging\typescript-df4be189\loc\lcl\CHS\TypeScriptLanguageService'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\HP PC\Desktop\joplin\packages\lib\node_modules.staging\aws-sdk-000adec5\lib\region_config_data.json'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\HP PC\Desktop\joplin\packages\lib\node_modules.staging\typescript-df4be189\loc\lcl\DEU\TypeScriptLanguageService\Microsoft.CodeAnalysis.TypeScript.EditorFeatures.dll.lcl'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\HP PC\Desktop\joplin\packages\lib\node_modules.staging\aws-sdk-000adec5\scripts\lib\ts-customizations.json'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\HP PC\Desktop\joplin\packages\lib\node_modules.staging\aws-sdk-000adec5\scripts\changelonpm ERR! C:/Program Files/Git/mingw64/libexec/git-core\git-submodule: line 22: .: git-sh-setup: file not found
npm ERR!
npm ERR! A complete log of this run can be found in:npm ERR! C:\Users\HP PC\AppData\Roaming\npm-cache_logs\2021-02-25T16_54_05_353Z-debug.log

lerna ERR! npm install exited 1 in '@joplin/lib'
lerna WARN complete Waiting for 7 child processes to exit. CTRL-C to exit immediately.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! root@ bootstrap: lerna bootstrap --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\HP PC\AppData\Roaming\npm-cache_logs\2021-02-25T16_54_07_241Z-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\HP PC\AppData\Roaming\npm-cache_logs\2021-02-25T16_54_08_327Z-debug.log

nikhilgupta2001 · 25 February 2021 17:12

$ node --version
v12.19.0

laurent · 25 February 2021 17:14

It's possible that the space in your username "HP PC" breaks some of the modules. Maybe try again from a path where there's no space.

nikhilgupta2001 · 26 February 2021 11:10

Now I am getting this

HP PC@LAPTOP-DUJ3LHP8 MINGW64 /d/joplin (dev)
$ npm install

husky@3.1.0 install D:\joplin\node_modules\husky
node husky install

husky > Setting up git hooks
husky > Done

husky@3.1.0 postinstall D:\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:

Contribute - Open Collective

root@ postinstall D:\joplin
npm run bootstrap --no-ci && npm run build

root@ bootstrap D:\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 1 in '@joplin/lib'
lerna ERR! npm install stderr:
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\jest-environment-node-fbeaee75\build\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\jest-environment-node-fbeaee75\package.json'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\basic.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\jest-environment-node-fbeaee75\build\index.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\except.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\index.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\readable-stream-fffc8c05\doc\wg-meetings\2015-01-30.md'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\readable-stream-43816691\doc\wg-meetings\2015-01-30.md'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\uc.micro-b0b1a8f7\categories\Cc\regex.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\literal-union.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\merge-exclusive.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\merge.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\mutable.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\opaque.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\uglify-js-ecfdd07f\lib\ast.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\package-json.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\partial-deep.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\promisable.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\lib\duration\clone.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\readonly-deep.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\lib\moment\clone.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\require-at-least-one.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\lib\utils\compare-arrays.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\lib\moment\compare.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\require-exactly-one.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\lib\units\constants.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\set-optional.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\lib\duration\constructor.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\immer-cb8d92f1\dist\immer.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\type-fest-45769bb3\source\set-required.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\lib\locale\constructor.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\lib\moment\constructor.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\uri-js-3d491f53\dist\esnext\schemes\http.js.map'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\lib\duration\create.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\uri-js-3d491f53\dist\esnext\schemes\https.js.map'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\lib\moment\creation-data.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\immer-cb8d92f1\dist\core\immerClass.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\jsdom-ad96d385\lib\jsdom\living\generated\Blob.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\dist\locale\cs.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\immer-cb8d92f1\src\core\immerClass.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\uri-js-3d491f53\dist\esnext\schemes\mailto.js.map'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\jsdom-ad96d385\lib\jsdom\living\generated\BlobPropertyBag.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\locale\cs.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\immer-cb8d92f1\dist\internal.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\jsdom-ad96d385\lib\jsdom\living\range\boundary-point.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\jsdom-ad96d385\lib\jsdom\living\generated\CanPlayTypeResult.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\locale\cs.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\immer-cb8d92f1\dist\plugins\mapset.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\dist\locale\cv.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\immer-cb8d92f1\src\plugins\mapset.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\uri-js-3d491f53\dist\es5\uri.all.js.map'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\locale\cv.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\src\locale\cv.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\immer-cb8d92f1\dist\plugins\patches.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\moment-7f6841ef\dist\locale\cy.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\immer-cb8d92f1\src\plugins\patches.ts'
npm WARN tar ENOENT: no such file or directory, open
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\codeartifact.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\codebuild.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\codecommit.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\codedeploy.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\codeguruprofiler.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\codegurureviewer.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\codepipeline.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\codestar.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\codestarconnections.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\codestarnotifications.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\cognitoidentity.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\lib\services\cognitoidentity.js'
npm WARN tar ENOENT: no such file or directory, open
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\resourcegroups.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\resourcegroupstaggingapi.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\robomaker.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\route53.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\lib\services\route53.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\route53domains.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\route53resolver.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\clients\s3.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\joplin\packages\lib\node_modules.staging\aws-sdk-583e8e40\lib\services\s3.js'

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\HP PC\AppData\Roaming\npm-cache_logs\2021-02-26T11_04_39_385Z-debug.log

lerna ERR! npm install exited 1 in '@joplin/lib'
lerna WARN complete Waiting for 7 child processes to exit. CTRL-C to exit immediately.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! root@ bootstrap: lerna bootstrap --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\HP PC\AppData\Roaming\npm-cache_logs\2021-02-26T11_04_50_494Z-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\HP PC\AppData\Roaming\npm-cache_logs\2021-02-26T11_04_50_604Z-debug.log

roman_r_m · 26 February 2021 12:44

I'm no expert on npm but try removing node_modules and package-lock.json in packages/lib and running npm i from there.

Also next time please wrap any logs in 3 backticks so it looks

like this

nikhilgupta2001 · 26 February 2021 13:32

I have installed in packages/lib it was successfull but npm start is not working

HP PC@LAPTOP-DUJ3LHP8 MINGW64 /d/joplin/packages/app-cli (dev)
$ npm start

> joplin@1.8.0 start D:\joplin\packages\app-cli
> gulp build -L && node "build/main.js" --stack-trace-enabled --log-level debug --env dev

Error: Cannot find module '@joplin/tools/gulp/utils'
Require stack:
- D:\joplin\packages\app-cli\gulpfile.js
- C:\Users\HP PC\AppData\Roaming\npm\node_modules\gulp-cli\lib\shared\require-or-import.js
- C:\Users\HP PC\AppData\Roaming\npm\node_modules\gulp-cli\lib\versioned\^4.0.0\index.js
- C:\Users\HP PC\AppData\Roaming\npm\node_modules\gulp-cli\index.js
- C:\Users\HP PC\AppData\Roaming\npm\node_modules\gulp-cli\bin\gulp.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:831:15)
    at Function.Module._load (internal/modules/cjs/loader.js:687:27)
    at Module.require (internal/modules/cjs/loader.js:903:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (D:\joplin\packages\app-cli\gulpfile.js:3:15)
    at Module._compile (internal/modules/cjs/loader.js:1015:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10)
    at Module.load (internal/modules/cjs/loader.js:879:32)
    at Function.Module._load (internal/modules/cjs/loader.js:724:14)
    at Module.require (internal/modules/cjs/loader.js:903:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'D:\\joplin\\packages\\app-cli\\gulpfile.js',
    'C:\\Users\\HP PC\\AppData\\Roaming\\npm\\node_modules\\gulp-cli\\lib\\shared\\require-or-import.js',
    'C:\\Users\\HP PC\\AppData\\Roaming\\npm\\node_modules\\gulp-cli\\lib\\versioned\\^4.0.0\\index.js',
    'C:\\Users\\HP PC\\AppData\\Roaming\\npm\\node_modules\\gulp-cli\\index.js',
    'C:\\Users\\HP PC\\AppData\\Roaming\\npm\\node_modules\\gulp-cli\\bin\\gulp.js'
  ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! joplin@1.8.0 start: `gulp build -L && node "build/main.js" --stack-trace-enabled --log-level debug --env dev`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the joplin@1.8.0 start 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\HP PC\AppData\Roaming\npm-cache\_logs\2021-02-26T13_28_34_017Z-debug.log```

nikhilgupta2001 · 26 February 2021 16:27

@laurent @roman_r_m
can you please help me.

roman_r_m · 26 February 2021 17:33

Does npm install from the root complete successfully now?

nikhilgupta2001 · 26 February 2021 18:15

not completely successfull from the root.
@roman_r_m

roman_r_m · 26 February 2021 19:28

And the error is?

nikhilgupta2001 · 27 February 2021 10:13

$ npm install
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated mkdirp-promise@5.0.1: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported

> husky@3.1.0 install C:\Users\HP PC\Desktop\joplin\node_modules\husky
> node husky install

husky > Setting up git hooks
husky > Done

> husky@3.1.0 postinstall C:\Users\HP PC\Desktop\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


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


> root@ bootstrap C:\Users\HP PC\Desktop\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 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@1.8.0~postinstall: @joplin/app-desktop@1.8.0
lerna info lifecycle @joplin/app-mobile@0.8.9~postinstall: @joplin/app-mobile@0.8.9

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


> core-js@2.6.11 postinstall C:\Users\HP PC\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 ( https://github.com/zloirock/core-js ) 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 
> https://www.patreon.com/zloirock 

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)


> core-js@3.6.4 postinstall C:\Users\HP PC\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\HP PC\Desktop\joplin\packages\app-clipper\popup\node_modules\core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"

npm WARN rollback Rolling back readable-stream@2.3.6 failed (this is probably harmless): EPERM: operation not permitted, lstat 'C:\Users\HP PC\Desktop\joplin\packages\app-clipper\popup\node_modules\jest-haste-map\node_modules\fsevents\node_modules'

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


> joplin-webclipper-popup@0.1.0 build C:\Users\HP PC\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:

  48.12 KB  build\static\js\2.chunk.js
  7.52 KB   build\static\js\main.chunk.js
  775 B     build\static\js\runtime-main.js
  746 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.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules\webpack-dev-server\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules\watchpack\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.12 (node_modules\react-scripts\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules\jest-haste-map\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 1852 packages from 869 contributors and audited 2131 packages in 262.296s

60 packages are looking for funding
  run `npm fund` for details

found 8833 vulnerabilities (8778 low, 33 moderate, 22 high)
  run `npm audit fix` to fix them, or `npm audit` for details

> @joplin/app-desktop@1.8.0 postinstall C:\Users\HP PC\Desktop\joplin\packages\app-desktop
> npm run build


> @joplin/app-desktop@1.8.0 build C:\Users\HP PC\Desktop\joplin\packages\app-desktop
> gulp build

C:/Users/HP PC/Desktop/joplin
[16:50:51] Using gulpfile ~\Desktop\joplin\packages\app-desktop\gulpfile.js
[16:50:51] Starting 'build'...
[16:50:51] Starting 'compileScripts'...
[16:50:51] Starting 'compilePackageInfo'...
[16:50:51] Starting 'copyPluginAssets'...
[16:50:51] Starting 'copyTinyMceLangs'...
[16:50:51] Starting 'updateIgnoredTypeScriptBuild'...
Compiling C:\Users\HP PC\Desktop\joplin\packages\app-desktop\tools/../gui/ClipperConfigScreen.jsx...

'C:\Users\HP' is not recognized as an internal or external command,
operable program or batch file.

[16:50:51] The following tasks did not complete: build, compileScripts, compilePackageInfo, copyPluginAssets, copyTinyMceLangs, updateIgnoredTypeScriptBuild
[16:50:51] Did you forget to signal async completion?
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @joplin/app-desktop@1.8.0 build: `gulp build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @joplin/app-desktop@1.8.0 build 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\HP PC\AppData\Roaming\npm-cache\_logs\2021-02-27T11_20_51_128Z-debug.log
lerna info lifecycle @joplin/app-desktop@1.8.0~postinstall: Failed to exec postinstall script

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

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! root@ bootstrap: `lerna bootstrap --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\HP PC\AppData\Roaming\npm-cache\_logs\2021-02-27T11_20_51_331Z-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\HP PC\AppData\Roaming\npm-cache\_logs\2021-02-27T11_20_51_425Z-debug.log

nikhilgupta2001 · 27 February 2021 10:13

@roman_r_m

roman_r_m · 27 February 2021 12:30

Seems to be a problem with your username having space in it as Laurent has said before

'C:\Users\HP' is not recognized as an internal or external command,
operable program or batch file.

Also, you don't need to mention me (with @) every time you reply, just use the reply button under a comment and the author of that comment will be notified.

nikhilgupta2001 · 5 March 2021 16:58


> @joplin/app-desktop@1.8.0 start /home/user/Desktop/joplin/packages/app-desktop
> gulp build && electron . --env dev --log-level debug --no-welcome --open-dev-tools

/home/user/Desktop/joplin/packages/app-desktop/node_modules
[22:27:20] Using gulpfile ~/Desktop/joplin/packages/app-desktop/gulpfile.js
[22:27:20] Starting 'build'...
[22:27:20] Starting 'compileScripts'...
[22:27:20] Starting 'compilePackageInfo'...
[22:27:20] Starting 'copyPluginAssets'...
[22:27:20] Starting 'copyTinyMceLangs'...
[22:27:20] Starting 'updateIgnoredTypeScriptBuild'...
Copying to /home/user/Desktop/joplin/packages/app-desktop/tools/../gui/note-viewer/pluginAssets
Copying /home/user/Desktop/joplin/packages/app-desktop/tools/../../../Assets/TinyMCE/langs => /home/user/Desktop/joplin/packages/app-desktop/tools/../node_modules/tinymce/langs
[22:27:26] Finished 'compileScripts' after 5.98 s
[22:27:26] Finished 'compilePackageInfo' after 5.99 s
[22:27:26] 'updateIgnoredTypeScriptBuild' errored after 5.99 s
[22:27:26] Error: ENOENT: no such file or directory, open '/home/user/Desktop/joplin/packages/app-desktop/node_modules/.gitignore'
[22:27:26] 'build' errored after 5.99 s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @joplin/app-desktop@1.8.0 start: `gulp build && electron . --env dev --log-level debug --no-welcome --open-dev-tools`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @joplin/app-desktop@1.8.0 start 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!     /home/user/.npm/_logs/2021-03-05T16_57_26_136Z-debug.log

HOw should i solve this npm install in root is successfull

roman_r_m · 5 March 2021 17:31

Are you running npm install from packages/app-desktop?

You shouldn't do it, not only it's not needed, it also breaks something and you need to run npm i from root again to fix it.

laurent · 5 March 2021 17:45

@nikhilgupta2001, again you didn't post what command you've executed or from which directory.

nikhilgupta2001 · 5 March 2021 17:48

i have done this because it was showing to have gulp not found error

nikhilgupta2001 · 5 March 2021 17:55

it worked now ..thanku so muchh

Topic		Replies	Views
I cant run npm install Development	13	9887	21 September 2021
Error on running npm install on root folder Development	9	2772	27 July 2021
Difficulty in setting up the development environment Support	2	812	15 April 2021
Npm build error on MacOS ARM Development	3	1009	6 November 2021
Can't build Joplin in Ubuntu 20.04 using npm install Development	1	1060	7 May 2021

Error While Setting up

Related topics