Yeoman generator not getting installed in VDI - installation

Trying to install(with Admin privileges) the Yeoman using "npm install -g yo generator-office" in VDI for Office Word Add-in
All the proxies and registry are set properly for the VDI, still facing the issue with below error.
npm install -g yo generator-office
npm WARN deprecated opn#6.0.0: The package has been renamed to open
npm WARN deprecated request#2.88.2: request has been deprecated, see request/request#3142
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
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 cross-spawn-async#2.2.5: cross-spawn no longer requires a build toolchain, use it instead
C:\Users\Administrator\AppData\Roaming\npm\yo-complete -> C:\Users\Administrator\AppData\Roaming\npm\node_modules\yo\lib\completion\index.js
C:\Users\Administrator\AppData\Roaming\npm\yo -> C:\Users\Administrator\AppData\Roaming\npm\node_modules\yo\lib\cli.js
yo#3.1.1 postinstall C:\Users\Administrator\AppData\Roaming\npm\node_modules\yo
yodoctor
Yeoman Doctor
Running sanity checks on your system
√ No .bowerrc file in home directory
√ Global configuration file is valid
√ NODE_PATH matches the npm root
√ No .yo-rc.json file in home directory
√ Node.js version
ErrorClass [RequestError]: getaddrinfo ENOTFOUND registry.npmjs.org
at ClientRequest. (C:\Users\Administrator\AppData\Roaming\npm\node_modules\yo\node_modules\latest-version\node_modules\got\index.js:73:21)
at Object.onceWrapper (events.js:313:26)
at ClientRequest.emit (events.js:223:5)
at ClientRequest.EventEmitter.emit (domain.js:475:20)
at Socket.socketErrorListener (_http_client.js:406:9)
at Socket.emit (events.js:223:5)
at Socket.EventEmitter.emit (domain.js:475:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:81:21) {
code: 'ENOTFOUND',
message: 'getaddrinfo ENOTFOUND registry.npmjs.org',
host: 'registry.npmjs.org'
hostname: 'registry.npmjs.org',
method: 'GET',
path: '/yo'
}
× yo version
ErrorClass [RequestError]: getaddrinfo ENOTFOUND registry.npmjs.org
at ClientRequest.
(C:\Users\Administrator\AppData\Roaming\npm\node_modules\yo\node_modules\latest-version\node_modules\got\index.js:73:21)
at Object.onceWrapper (events.js:313:26)
at ClientRequest.emit (events.js:223:5)
at ClientRequest.EventEmitter.emit (domain.js:475:20)
at Socket.socketErrorListener (_http_client.js:406:9)
at Socket.emit (events.js:223:5)
at Socket.EventEmitter.emit (domain.js:475:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:81:21) {
code: 'ENOTFOUND',
message: 'getaddrinfo ENOTFOUND registry.npmjs.org',
host: 'registry.npmjs.org',
hostname: 'registry.npmjs.org',
method: 'GET',
path: '/yo'
}
Found potential issues on your machine
generator-office#1.7.6
yo#3.1.1
updated 2 packages in 194.549s

Related

Laravel NPM fixing cross-env problem leading to problem 'enoent spawn bash ENOENT'

I've been struggling to fix the common 'cross-env' is not recognized as an internal or external command, problem with NPM in a Laravel 9.x project on a Windows 10 machine. I've gone over most of the other similar topics but I can't find a solution that works and I'm not familiar with yarn which is what a lot of the answers involve.
npm install -g cross-env was used but trying to run NPM then gave a path error:
> development
> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-mde_modules/laravel-mix/setup/webpack.config.js
The system cannot find the path specified.
node:events:491
throw er; // Unhandled 'error' event
^
Error: spawn node_modules\webpack\bin\webpack.js ENOENT
at notFoundError (C:\Users\Tobias\AppData\Roaming\npm\node_modules\cross-env\node_molib\enoent.js:6:26)
at verifyENOENT (C:\Users\Tobias\AppData\Roaming\npm\node_modules\cross-env\node_modib\enoent.js:40:16)
at cp.emit (C:\Users\Tobias\AppData\Roaming\npm\node_modules\cross-env\node_modules\oent.js:27:25)
Emitted 'error' event on ChildProcess instance at:
at cp.emit (C:\Users\Tobias\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:30:37)
at ChildProcess._handle.onexit (node:internal/child_process:291:12) {
code: 'ENOENT',
errno: 'ENOENT',
path: 'node_modules\\webpack\\bin\\webpack.js',
spawnargs: [
'--progress',
'--hide-modules',
'--config=node_modules/laravel-mix/setup/webpack.config.js'
]
}
Node.js v18.12.1`
To solve this I used the command npm config set script-shell bash as suggested here
But this then gives a 'NOENT' problem that I can't find a good solution for to fix (or revert back)
> development
> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-m
npm ERR! code ENOENT
npm ERR! syscall spawn bash
npm ERR! path C:\xampp\htdocs\antheap
npm ERR! errno -4058
npm ERR! enoent spawn bash ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Tobias\AppData\Local\npm-cache\_logs\2022-12-22T09_34_44_288Z-debug-0.log
here is the logfile
0 verbose cli C:\Program Files\nodejs\node.exe C:\Users\Tobias\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
1 info using npm#8.11.0
2 info using node#v18.12.1
3 timing npm:load:whichnode Completed in 1ms
4 timing config:load:defaults Completed in 2ms
5 timing config:load:file:C:\Users\Tobias\AppData\Roaming\npm\node_modules\npm\npmrc Completed in 3ms
6 timing config:load:builtin Completed in 3ms
7 timing config:load:cli Completed in 1ms
8 timing config:load:env Completed in 1ms
9 timing config:load:file:C:\xampp\htdocs\antheap\.npmrc Completed in 0ms
10 timing config:load:project Completed in 2ms
11 timing config:load:file:C:\Users\Tobias\.npmrc Completed in 0ms
12 timing config:load:user Completed in 0ms
13 timing config:load:file:C:\Users\Tobias\AppData\Roaming\npm\etc\npmrc Completed in 0ms
14 timing config:load:global Completed in 0ms
15 timing config:load:validate Completed in 1ms
16 timing config:load:credentials Completed in 0ms
17 timing config:load:setEnvs Completed in 1ms
18 timing config:load Completed in 12ms
19 timing npm:load:configload Completed in 12ms
20 timing npm:load:mkdirpcache Completed in 1ms
21 timing npm:load:mkdirplogs Completed in 0ms
22 verbose title npm run development
23 verbose argv "run" "development"
24 timing npm:load:setTitle Completed in 1ms
25 timing config:load:flatten Completed in 2ms
26 timing npm:load:display Completed in 3ms
27 verbose logfile logs-max:10 dir:C:\Users\Tobias\AppData\Local\npm-cache\_logs
28 verbose logfile C:\Users\Tobias\AppData\Local\npm-cache\_logs\2022-12-22T09_34_44_288Z-debug-0.log
29 timing npm:load:logFile Completed in 15ms
30 timing npm:load:timers Completed in 0ms
31 timing npm:load:configScope Completed in 0ms
32 timing npm:load Completed in 34ms
33 silly logfile start cleaning logs, removing 2 files
34 timing command:run Completed in 8ms
35
35 verbose stack at ChildProcess._handle.onexit (node:internal/child_process:283:19)
35 verbose stack at onErrorNT (node:internal/child_process:476:16)
35 verbose stack at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
36 verbose cwd C:\xampp\htdocs\antheap
37 verbose Windows_NT 10.0.19044
38 verbose node v18.12.1
39 verbose npm v8.11.0
40 error code ENOENT
41 error syscall spawn bash
42 error path C:\xampp\htdocs\antheap
43 error errno -4058
44 error enoent spawn bash ENOENT
45 error enoent This is related to npm not being able to find a file.
45 error enoent
46 verbose exit -4058
47 timing npm Completed in 54ms
48 verbose code -4058
49 error A complete log of this run can be found in:
49 error C:\Users\Tobias\AppData\Local\npm-cache\_logs\2022-12-22T09_34_44_288Z-debug-0.log
I saw a suggesting to use npm ci but this didn't work. I've also reinstalled Node.js, and ran npm install, both to no effect.
Deleting and reinstalling NPM within the app doesn't help either. I also show a host of other possible issues (like the old lock file which it however never seems to update properly),
PS C:\xampp\htdocs\antheap> npm install
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN deprecated har-validator#5.1.3: this library is no longer supported
npm WARN deprecated chokidar#2.1.6: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated browserslist#2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated debug#4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug#4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated extract-text-webpack-plugin#3.0.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-url#0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated flatten#1.0.2: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated source-map-resolve#0.5.2: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated uuid#3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated acorn-dynamic-import#2.0.2: This is probably built in to whatever tool you're using. If you still need it... idk
npm WARN deprecated browserslist#1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated uglify-es#3.3.9: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
npm WARN deprecated mkdirp#0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated browserslist#1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated browserslist#1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated axios#0.18.1: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated popper.js#1.15.0: You can find the new Popper v2 at #popperjs/core, this package is dedicated to the legacy v1
npm WARN deprecated buffer#4.9.1: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer
npm WARN deprecated svgo#0.7.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated tar#2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated core-js#2.6.9: core-js#<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code ENOENT
npm ERR! syscall spawn bash
npm ERR! path C:\xampp\htdocs\antheap\node_modules\node-sass
npm ERR! errno -4058
npm ERR! enoent spawn bash ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Tobias\AppData\Local\npm-cache\_logs\2022-12-22T09_52_52_967Z-debug-0.log

Strapi Graphql Plugin Crashes Strapi Server

I just tried to install the graphql plugin for strapi (i.e., strapi-plugin-graphql). When I tried to install it via the admin interface, I got the following error message:
The restart takes longer than expected
The server should have restarted, please check your logs in the terminal
When I check my terminal, this is what I see:
[2019-12-27T07:47:12.612Z] debug GET /admin/plugins (5 ms) 200
[2019-12-27T07:47:15.882Z] info Installing graphql...
[2019-12-27T07:48:59.105Z] info File changed: C:\code\tutorials\react\Gatsby\strapi\startup-reporter\package.json[2019-12-27T07:48:59.279Z] debug POST /admin/plugins/install (103411 ms) 200
[2019-12-27T07:48:59.281Z] info The server is restarting
[2019-12-27T07:49:14.672Z] debug ⛔️ Server wasn't able to start properly.
[2019-12-27T07:49:14.674Z] error Error: Field "Query.news" can only be defined once.
at assertValidSDL (C:\code\tutorials\react\Gatsby\strapi\startup-reporter\node_modules\graphql\validation\validate.js:108:11)
at Object.buildASTSchema (C:\code\tutorials\react\Gatsby\strapi\startup-reporter\node_modules\graphql\utilities\buildASTSchema.js:71:34)
at Object.buildSchemaFromTypeDefinitions (C:\code\tutorials\react\Gatsby\strapi\startup-reporter\node_modules\graphql-tools\dist\generate\buildSchemaFromTypeDefinitions.js:23:28)
at makeExecutableSchema (C:\code\tutorials\react\Gatsby\strapi\startup-reporter\node_modules\graphql-tools\dist\makeExecutableSchema.js:26:29)
at Object.generateSchema (C:\code\tutorials\react\Gatsby\strapi\startup-reporter\node_modules\strapi-plugin-graphql\services\Schema.js:300:22)
at Object.initialize (C:\code\tutorials\react\Gatsby\strapi\startup-reporter\node_modules\strapi-plugin-graphql\hooks\graphql\index.js:59:50)
at Promise.resolve.then (C:\code\tutorials\react\Gatsby\strapi\startup-reporter\node_modules\strapi\lib\hooks\index.js:37:28)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! startup-reporter#0.1.0 dev: `strapi develop`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the startup-reporter#0.1.0 dev 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\moshe\AppData\Roaming\npm-cache\_logs\2019-12-27T07_49_14_697Z-debug.log
Any idea why I am getting this error message and how to fix it?
UPDATE:
I should note that I did a fresh install of strapi and then installed the graphql plugin -- and it installed properly. It only didn't work with an installation that already had custom post types. I don't know why that is -- and what I can do to install it with those custom post types. Any ideas?
Here is the issue about this problem
https://github.com/strapi/strapi/issues/1198
Some words are not well managed for the pluralize version.
So the issue is due to that point.
There is currently nothing to do to fix it by your own.

Cannot run addon after installation of web-ext on ubuntu 16.04 nodejs v4.2.6 npm 3.5.2

when installing web-ext i got this two messages in the and of installation:
npm WARN optional Skipping failed optional dependency /web-ext/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents#1.2.4
after trying to start addon with web-ext run i get this messages
TypeError: Cannot read property 'R_OK' of undefined
at fileIsReadable (/usr/local/lib/node_modules/web-ext/dist/webpack:/src/util/file-exists.js:24:42)
at _callee$ (/usr/local/lib/node_modules/web-ext/dist/webpack:/src/util/file-exists.js:28:11)
at tryCatch (/usr/local/lib/node_modules/web-ext/node_modules/regenerator-runtime/runtime.js:62:40)
at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/web-ext/node_modules/regenerator-runtime/runtime.js:296:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as next]
(/usr/local/lib/node_modules/web-ext/node_modules/regenerator-runtime/runtime.js:114:21)
at step (/usr/local/lib/node_modules/web-ext/dist/webpack:/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:1)
at /usr/local/lib/node_modules/web-ext/dist/webpack:/node_modules/babel-runtime/helpers/asyncToGenerator.js:35:1
at new Promise (/usr/local/lib/node_modules/web-ext/dist/webpack:/node_modules/core-js/library/modules/es6.promise.js:177:1)
at /usr/local/lib/node_modules/web-ext/dist/webpack:/node_modules/babel-runtime/helpers/asyncToGenerator.js:14:1
at fileExists (/usr/local/lib/node_modules/web-ext/dist/web-ext.js:13002:17)
Update to at least the latest v6 of node. I recommend you to use >= v8, because the support for v6 is ending in 2019 and you can't use async/await for example. (https://github.com/nodejs/Release#release-schedule)

Installation LoopBack-CLI error node-gyp rebuild

Hi Im installing the loopback-cli.
Running these commands:
npm install --global --production windows-build-tools
AND
npm install -g loopback-cli
The second command run rebuilding the ursa module into error. There is some link to C:\OpenSSL-Win64. What the ... is this? Some hardcoded library link?
Write me please some way how to install normally the loopback. This is from their installation site. Thanx.
Here the log:
C:\Users\Erik\AppData\Roaming\npm\node_modules\loopback-cli\node_modules\ursa>if not defined npm_config_node_gyp (node "C:\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
ursaNative.cc
win_delay_load_hook.cc
..\src\ursaNative.cc(157): warning C4244: 'argument': conversion from 'ssize_t' to 'int', possible loss of data [C:\Use
rs\Erik\AppData\Roaming\npm\node_modules\loopback-cli\node_modules\ursa\build\ursaNative.vcxproj]
..\src\ursaNative.cc(172): warning C4244: 'argument': conversion from 'ssize_t' to 'int', possible loss of data [C:\Use
rs\Erik\AppData\Roaming\npm\node_modules\loopback-cli\node_modules\ursa\build\ursaNative.vcxproj]
LINK : fatal error LNK1181: cannot open input file 'C:\OpenSSL-Win64\lib\libeay32.lib' [C:\Users\Erik\AppData\Roaming\n
pm\node_modules\loopback-cli\node_modules\ursa\build\ursaNative.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:258:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.15063
gyp ERR! command "C:\\nodejs\\node.exe" "C:\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\Erik\AppData\Roaming\npm\node_modules\loopback-cli\node_modules\ursa
gyp ERR! node -v v8.9.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa#0.9.4 (node_modules\loopback-cli\node_modules\ursa):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa#0.9.4 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
+ loopback-cli#4.0.0
added 3 packages and updated 1 package in 27.638s
Same issue here.
Setup before fixing:
lb -v 4.2.1 (generator-loopback#5.9.4 loopback-workspace#4.5.0)
node -v v10.13.0
OS: Windows 10 Home
I was able to fix the issue after taking the following steps:
Install node v8.12.0
Install OpenSSL 1.1 in C:\OpenSSL-Win64 (strong-ursa hard codes the location)
Create a symbolic link in C:\OpenSSL-Win64\lib named libeay64.lib which targets libcrypto.lib.
Run npm i -g windows-build-tools
Run npm i -g looback-cli again.
I'm not sure if rolling back the NodeJS version to 8.12 is necessary. There are a few widely, albeit not well documented pain points working with Loopback due to strong-ursa's use of native libraries. (Please note, this is unconfirmed information as I'm in a hurry to get back to developing the project at hand.) These steps allowed me to continue using Loopback CLI unhindered.
Useful links:
Download previous NodeJS releases: https://nodejs.org/en/download/releases/
Download OpenSSL: https://slproweb.com/products/Win32OpenSSL.html
windows-build-tools: https://github.com/felixrieseberg/windows-build-tools
https://github.com/curl/curl/issues/984
https://github.com/strongloop/loopback-cli/issues/36#issuecomment-434331508

Appcelerator Error when building a new project for iOS

I just updated appcelerator after not working with it for a few months. I created a new project and attempted to build it for iPad Air (v10.2) It completely fails to build with the following errors:
2017-03-02T16:18:01.679Z | DEBUG | Titanium Downloads Last Checked: 1488468509275
2017-03-02T16:18:03.713Z | ERROR | An uncaught exception was thrown!
Rebuild failed:
2017-03-02T16:18:03.714Z | ERROR | Rebuild failed:
node-pre-gyp http GET https://appc-node-binaries.s3.amazonaws.com/node-ios-device/v0.11.2/node_ios_device-v0.11.2-node-v51-darwin-x64.tar.gz
node-pre-gyp http 404 https://appc-node-binaries.s3.amazonaws.com/node-ios-device/v0.11.2/node_ios_device-v0.11.2-node-v51-darwin-x64.tar.gz
node-pre-gyp ERR! Tried to download: https://appc-node-binaries.s3.amazonaws.com/node-ios-device/v0.11.2/node_ios_device-v0.11.2-node-v51-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for node-ios-device#0.11.2 and node#7.4.0 (node-v51 ABI) (falling back to source compile with node-gyp)
node-pre-gyp http Pre-built binary not available for your system, looked for https://appc-node-binaries.s3.amazonaws.com/node-ios-device/v0.11.2/node_ios_device-v0.11.2-node-v51-darwin-x64.tar.gz
node-pre-gyp ERR! build error
My node version is 7.4.0
Any thoughts?
Ok answering my own question here again.
Not sure why I am getting the 404 trying to get the module, but I resolved this by changing directory to
~/Library/Application Support/Titanium/mobilesdk/osx/6.0.2.GA/node_modules
then running:
npm install node-ios-device
not sure if this will help anyone else out but it got me over the hump.

Resources