You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 9, 2024. It is now read-only.
Getting the java error when trying to push the Node JS code to the PC.
The Node JS Code internally connects to the teradata to pull the table details.
I have added the reference of the package.json and the error which i am getting.
Error----
node-gyp rebuild
[node-java] Error: not found: javac
gyp: Call to 'node findJavaHome.js' returned exit status 1 while in binding.gyp.
while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/tmp/contents574403284/deps/0/node/
lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:336:16)
gyp ERR! stack at ChildProcess.emit (events.js:160:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_proces
s.js:209:12)
Hi, I am facing a similar issue. I am in the midst of developing a NodeJS API to be deployed to PCF that requires me to query a Teradata DB. Did you manage to get a workaround? Any chances you can help me out or guide me.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Getting the java error when trying to push the Node JS code to the PC.
The Node JS Code internally connects to the teradata to pull the table details.
I have added the reference of the package.json and the error which i am getting.
Error----
Package.json----
{
"name": "first_app",
"version": "1.0.0",
"description": "node app",
"author": "NA",
"contributors": "",
"dependencies": {
"java": "^0.9.0",
"body-parser": "^1.18.2",
"build-tools": "^7.2.4",
"cfenv": "^1.0.4",
"express": "^4.16.2",
"teradata": "^0.1.1"
},
"repository": {},
"main": "server1.js",
"engines": {
"node": "9.5.0"
},
"keywords": []
}
The text was updated successfully, but these errors were encountered: