Skip to content

Instantly share code, notes, and snippets.

@rluvaton
Created August 12, 2022 14:55
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save rluvaton/9e96419f8a5371b7921d6b432ee7ec1f to your computer and use it in GitHub Desktop.
Save rluvaton/9e96419f8a5371b7921d6b432ee7ec1f to your computer and use it in GitHub Desktop.
Error in practicajs generate app
DEBUG=* npx @practica/create-node-app interactive

npx: installed 368 in 14.066s
(node:25262) UnhandledPromiseRejectionWarning: Error: Command failed: npx turbo run build
 WARNING  cannot find a .git folder. Falling back to manual file hashing (which may be slower). If you are running this build in a pruned directory, you can ignore this message. Otherwise, please initialize a git repository in the root of your monorepo
@practica/jwt-token-verifier:build: ERROR: command finished with error: command (libraries/jwt-token-verifier) npm run build exited (1)
command (libraries/jwt-token-verifier) npm run build exited (1)

• Packages in scope: @practica/configuration-provider, @practica/error-handling, @practica/jwt-token-verifier, @practica/logger, @practica/validation, order-service
• Running build in 6 packages
@practica/jwt-token-verifier:build: cache miss, executing 65bb070783b26b9a
@practica/configuration-provider:build: cache miss, executing 93f3306199f83219
@practica/validation:build: cache miss, executing 396387be1f95436e
@practica/configuration-provider:build:
@practica/configuration-provider:build: > @practica/configuration-provider@0.0.1-alpha.3 build /Users/rluvaton/dev/open-source/practicajs/generate-tries/default-app-name/libraries/configuration-provider
@practica/configuration-provider:build: > tsc
@practica/configuration-provider:build:
@practica/jwt-token-verifier:build:
@practica/jwt-token-verifier:build: > @practica/jwt-token-verifier@0.0.1-alpha.5 build /Users/rluvaton/dev/open-source/practicajs/generate-tries/default-app-name/libraries/jwt-token-verifier
@practica/jwt-token-verifier:build: > tsc
@practica/jwt-token-verifier:build:
@practica/jwt-token-verifier:build: sh: tsc: command not found
@practica/jwt-token-verifier:build: npm ERR! code ELIFECYCLE
@practica/jwt-token-verifier:build: npm ERR! syscall spawn
@practica/jwt-token-verifier:build: npm ERR! file sh
@practica/jwt-token-verifier:build: npm ERR! errno ENOENT
@practica/jwt-token-verifier:build: npm ERR! @practica/jwt-token-verifier@0.0.1-alpha.5 build: `tsc`
@practica/jwt-token-verifier:build: npm ERR! spawn ENOENT
@practica/jwt-token-verifier:build: npm ERR!
@practica/jwt-token-verifier:build: npm ERR! Failed at the @practica/jwt-token-verifier@0.0.1-alpha.5 build script.
@practica/jwt-token-verifier:build: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
@practica/validation:build:
@practica/validation:build: > @practica/validation@0.0.1-alpha.1 build /Users/rluvaton/dev/open-source/practicajs/generate-tries/default-app-name/libraries/validation
@practica/validation:build: > tsc
@practica/validation:build:
@practica/jwt-token-verifier:build: npm WARN Local package.json exists, but node_modules missing, did you mean to install?
@practica/jwt-token-verifier:build:
@practica/jwt-token-verifier:build: npm ERR! A complete log of this run can be found in:
@practica/jwt-token-verifier:build: npm ERR!     /Users/rluvaton/.npm/_logs/2022-08-12T14_53_35_982Z-debug.log
@practica/logger:build: cache miss, executing 358b066c9c0598df
@practica/error-handling:build: cache miss, executing 07a49161dc4c35ea

 Tasks:    0 successful, 1 total
Cached:    0 cached, 1 total
  Time:    1.309s


    at makeError (/Users/rluvaton/.npm/_npx/25262/lib/node_modules/@practica/create-node-app/node_modules/execa/index.js:174:9)
    at /Users/rluvaton/.npm/_npx/25262/lib/node_modules/@practica/create-node-app/node_modules/execa/index.js:278:16
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:25262) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:25262) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  _____                          _     _
 |  __ \                        | |   (_)
 | |__) |  _ __    __ _    ___  | |_   _    ___    __ _
 |  ___/  | '__|  / _` |  / __| | __| | |  / __|  / _` |
 | |      | |    | (_| | | (__  | |_  | | | (__  | (_| |
 |_|      |_|     \__,_|  \___|  \__| |_|  \___|  \__,_|


🔁 Creating your app now. This might take a few seconds...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment