I'm trying to get my local environment working after cloning the react-admin repo.
I'm tried to run make install and make build as guided by the docs, but these won't work for me.
I install make globally. And yarn, npm and nodejs are all up-to-date. I'm on Windows-10 using Visual Studio Code with PowerShell terminal.This is what I get...
make install returns:
make i info Invoking install target
(node:7316) UnhandledPromiseRejectionWarning: undefined
(node:7316) 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: 1)
(node:7316) [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.
make × ERR not found: make-package.json
make build returns:
(node:9000) UnhandledPromiseRejectionWarning: undefined
(node:9000) 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: 1)
(node:9000) [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.
make × ERR not found: make-##
I really want to get started on my ra fix branch so any help would be appreciated.Hopefully, it's just a simple mistake on my end.
It's interesting to note that make is primarily a utility tool for the unix env.
Therefore running make commands is not a direct process in windows environment.
NMAKE is the official windows alternative that will help you achieve the same.
Related
I get this error:
Error: Can't find training file, please try to specify it with the --source option
I thought it was a file path issue, so I added source and still got an error:
(node:36619) UnhandledPromiseRejectionWarning: Can't parse json file "/Users/Cos-Ibe/Futo_Chatbot/data/data.json"
SyntaxError: Unexpected token in JSON at position 0
(Use `node --trace-warnings ...` to show where the warning was created)
(node:36619) 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: 1)
(node:36619) [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.
I am getting below warning message while building my react js project using CI
npm build fails with below message:
npm run build command contains --trace-warnings. But it has not trace exact location of warning.
(node:179) UnhandledPromiseRejectionWarning: Failed to compile server
at emitUnhandledRejectionWarning (internal/process/promises.js:170:15)
at processPromiseRejections (internal/process/promises.js:247:11)
at processTicksAndRejections (internal/process/task_queues.js:96:32) (node:179)
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: 1) (node:179) [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.
at emitDeprecationWarning (internal/process/promises.js:180:11)
at processPromiseRejections (internal/process/promises.js:249:13)
at processTicksAndRejections (internal/process/task_queues.js:96:32)
Is there a way I can ignore the warning during this process as I cannot find out the cause of this warning and not able to fix this.
Node version 10.16.3
npm version. 6.9.0
Using Jenkins for CI.
Message&trace:
Generating browser application bundles (phase: building)...(node:5312) UnhandledPromiseRejectionWarning: TypeError: MessagePort was found in message but not listed in transferList
at new Worker (internal/worker.js:170:17)
at SassWorkerImplementation.createWorker (C:\Users\shail\iacademiaApp1\node_modules\#angular-devkit\build-angular\src\sass\sass-service.js:96:24)
at SassWorkerImplementation.render (C:\Users\shail\iacademiaApp1\node_modules\#angular-devkit\build-angular\src\sass\sass-service.js:62:40)
at Object.loader (C:\Users\shail\iacademiaApp1\node_modules\sass-loader\dist\index.js:46:3)
(node:5312) 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: 1)
(node:5312) [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.
(node:5312) UnhandledPromiseRejectionWarning: TypeError: MessagePort was found in message but not listed in transferList
at new Worker (internal/worker.js:170:17)
at SassWorkerImplementation.createWorker (C:\Users\shail\iacademiaApp1\node_modules\#angular-devkit\build-angular\src\sass\sass-service.js:96:24)
at SassWorkerImplementation.render (C:\Users\shail\iacademiaApp1\node_modules\#angular-devkit\build-angular\src\sass\sass-service.js:62:40)
at Object.loader (C:\Users\shail\iacademiaApp1\node_modules\sass-loader\dist\index.js:46:3)
(node:5312) 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)
/ Generating browser application bundles (phase: building)...
The latest version of the Angular CLI (12.0.1) does not support Node below version 12.20.
Solution
Update your version of Node to the latest stable version
You should pick the version marked LTS, which at the time of writing is in the 14.x.x range.
Workaround
Only do this if you for some reason are completely unable to update your Node version
Add node-sass to your project devDependencies until you are able to update your version of node.
npm i -save-dev node-sass
yarn add -D node-sass
You should be careful with this workaround, as node-sass is going to be deprecated soon.
Please try this:
ng update #angular/cli
npm install
I installed aeproject by doing:
$ npm install -g aeproject
Initiallized my project with
$ aeproject init
And when I want to test it with
$ aeproject test
I get the following error:
(node:68448) UnhandledPromiseRejectionWarning:
/Users/meli/MyStuff/MyAE/ae_tutorial1/node_modules/aeproject-lib/dist/aeproject-deployer.js:1
Error: Cannot find module 'aeproject-utils' Require stack:
/Users/meli/MyStuff/MyAE/ae_tutorial1/node_modules/aeproject-lib/dist/aeproject-deployer.js
/Users/meli/MyStuff/MyAE/ae_tutorial1/node_modules/aeproject-lib/dist/index.js
/Users/meli/MyStuff/MyAE/ae_tutorial1/test/exampleTest.js
/usr/local/lib/node_modules/aeproject/node_modules/mocha/lib/mocha.js
/usr/local/lib/node_modules/aeproject/node_modules/mocha/index.js
/usr/local/lib/node_modules/aeproject/aeproject-test/aeproject-test.js
/usr/local/lib/node_modules/aeproject/aeproject-test/test.js
/usr/local/lib/node_modules/aeproject/commands.js
/usr/local/lib/node_modules/aeproject/aeproject-cli.js
at Object. (/Users/meli/MyStuff/MyAE/ae_tutorial1/node_modules/aeproject-lib/dist/aeproject-deployer.js:21:43)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10) (Use node --trace-warnings ... to show where the warning was created) (node:68448)
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:68448) [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.
You can fix this issue by doing
$ npm install aeproject-utils prompts aeproject-logger
I get the following error during installation of the Cordova OneSignal plugin:
UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): [object Object]
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.
I couldn't find any solutions on Google.