I am trying to run command npm run build. I am getting error
`make i info Invoking build target
make i info Invoking dist/build target
(node:15892) UnhandledPromiseRejectionWarning: undefined
(Use `node --trace-warnings ...` to show where the warning was created)
(node:15892) 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:15892) [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-$(SOURCE_FILES)`
Please anyone can help me to solve the problem.
I finally solved it installing make command using chocolaty in my window. I was getting error because make was not installed on my windows (I had no idea regarding that make is window's command not NodeJs').
This post helped me to solve my problem.
How to install and use "make" in Windows?
Related
My gatsby website was running locally without problems and when I tried to restart it today without updating the code, the npm run develop build succeeds. However, when I try to open localhost in browser, this error is thrown in the terminal:
success Building development bundle - 16.014s
success Writing page-data.json files to public directory - 0.103s - 3/11
106.93/s
(node:2043) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'split' of undefined
at parseError (/Users/sp/Documents/jamstack/training/frontend/node_modules/gatsby/src/utils/dev-ssr/render-dev-html-child.js:52:26)
at /Users/sp/Documents/jamstack/training/frontend/node_modules/gatsby/src/utils/dev-ssr/render-dev-html-child.js:106:27
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:2043) 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 rejeæction, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:2043) [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 can't seem to work out where this error is coming from as I did not change any of the code that was working earlier.
Does anyone have an idea?
There's no detail about the running version of Gatsby but according to this GitHub thread, while the issue is being fixed in the next release you can bypass it by installing a canary version:
npm i gatsby#webpack-split-fix
Im getting this error code with express API with typeorm database:
(node:23162) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 127.0.0.1:5432
at Object._errnoException (util.js:1022:11)
at _exceptionWithHostPort (util.js:1044:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14)
(node:23162) 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(). (rejection id: 1)
(node:23162) [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 used only this basic code in my app.ts and error is still on after sudo npm run build && sudo npm run start
createConnection().then(connection => {
console.log("Try");
});
I tried also to change connection to async, but still not working.
You simply cannot connect to the database for whatever reason. It's not an issue with the ORM itself. Check your configurations, because most definitely that's where the problem resides.
I'm trying:
vue-native init test-project
And I'm getting this output:
Using globally installed expo-cli 3.0.10
Creating Vue Native project project-new
Creating project with expo-cli
[09:09:29] --name: argument is required in non-interactive mode. √
Created project with expo-cli
(node:9072) UnhandledPromiseRejectionWarning: Error: ENOENT: no such
file or directory, chdir 'project-new'
at process.chdir (internal/process/main_thread_only.js:31:12)
at installPackages (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\src\index.js:182:11)
at createExpoProject (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\src\index.js:123:3)
at init (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\src\index.js:101:5)
at Command. (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\src\index.js:69:7)
at Command.listener (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\node_modules\commander\index.js:315:8)
at Command.emit (events.js:182:13)
at Command.parseArgs (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\node_modules\commander\index.js:651:12)
at Command.parse (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\node_modules\commander\index.js:474:21)
at Object. (C:\Users\User\AppData\Roaming\npm\node_modules\vue-native-cli\src\index.js:81:9)
(node:9072) 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(). (rejection id: 1) (node:9072) [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've already installed React Native CLI, Expo CLI, and Vue Native CLI. I tried to solve the issue by updating npm but it did not work.
Also when I run:
vue-native init test-project --no-crna
it is ok and no errors appear.
'i have installed android studio and installed all sdk tools and jdk 1.8 but still app is not building'
'(node:4216) 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(). (rejection id: 1)
(node:4216) [DEP0018] DeprecationWarning: Unhandled promise rejections are depre cated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.'
Try to use
ionic version 3.20.0
npm install -g ionic#3.20.0
NodeJS Version 8.11.3
https://nodejs.org/download/release/v8.11.3/
Download JDK Version 1.8.0_171
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html?printOnly=1
I hope it will work for you.
For some reason truffle is not recognizing the change in constructor size
Things I've tried
1) Uninstall truffle and reinstall
2) deleting the build folder and recompiling
When i run a test it complains but runs the test anyway
(node:97628) UnhandledPromiseRejectionWarning: Error: Factory contract constructor expected 3 arguments, received 2
at /usr/local/lib/node_modules/truffle/build/webpack:/packages/truffle-contract/contract.js:390:1
at new Promise (<anonymous>)
at /usr/local/lib/node_modules/truffle/build/webpack:/packages/truffle-contract/contract.js:374:1
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:160:7)
(node:97628) 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(). (rejection id: 2)
(node:97628) [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.
the second time I run the test it crashes truffle, so I have to reboot truffle after I get one test to run.
Error: Factory contract constructor expected 3 arguments, received 2
at /usr/local/lib/node_modules/truffle/build/webpack:/packages/truffle-contract/contract.js:390:1
at new Promise (<anonymous>)
at /usr/local/lib/node_modules/truffle/build/webpack:/packages/truffle-contract/contract.js:374:1
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:160:7)
It turns out that in my migrations folder I had not updated 2_deploy_contracts to use all three of the constructor arguments. It was hidden to me, because I was only running test testFile.js and didn't realize it ran this migration every time