Electron Browser Window won't open [duplicate] - electron

This question already has an answer here:
ElectronJs Quick Start not starting?
(1 answer)
Closed 4 years ago.
When I am executing npm command npm start it shows only this not opening an electron browser window.
firstdesktopapp#1.0.0 start E:\NodeJS Projects\ElectronJs\FirstDesktopAPp
electron .
here is my package.json code
{
"name": "firstdesktopapp",
"version": "1.0.0",
"description": "First Desktop App on Electron",
"main": "app.js",
"scripts": {
"start": "electron ."
},
"author": "Makhmoor Rehman",
"license": "NoN",
"devDependencies": {
"electron": "^4.0.0-nightly.20181010"
}
}
and here is my app.js code
const electron = require("electron");
const url = require("url");
const path = require("path");
const {app, BrowserWindow} = electron;
let mainWindow;
// Listen for app to be ready
app.on("ready", function() {
// Create new window
mainWindow = new BrowserWindow({});
//load html into window
mainWindow.loadURL(url.format({
pathname: path.join(__dirname, "index.html"),
protocol: "file:",
slashes: true,
}));
});
I have installed the latest version of electron and nodejs, I have a dell laptop and os Windows 10 64bit.
After killing the process of electron I am getting this.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! firstdesktopapp#1.0.0 start: electron .
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the firstdesktopapp#1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional
logging output ab ove.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\makhm\AppData\Roaming\npm-cache_logs\2018-10-31T01_10_09_481Z-debug.log
And in the debug file I am getting this
nfo it worked if it ends with ok
1 verbose cli [ 'E:\nodejs\node.exe',
1 verbose cli 'E:\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm#6.4.1
3 info using node#v11.0.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle firstdesktopapp#1.0.0~prestart: firstdesktopapp#1.0.0
6 info lifecycle firstdesktopapp#1.0.0~start: firstdesktopapp#1.0.0
7 verbose lifecycle firstdesktopapp#1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle firstdesktopapp#1.0.0~start: PATH:
E:\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;E:\NodeJS Projects\ElectronJs\FirstDesktopAPp\node_modules.bin;C:\Users\makhm\bin;E:\Git\mingw64\bin;E:\Git\usr\local\bin;E:\Git\usr\bin;E:\Git\usr\bin;E:\Git\mingw64\bin;E:\Git\usr\bin;C:\Users\makhm\bin;C:\Python27;C:\Python27\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\SYSTEM32;C:\WINDOWS;C:\WINDOWS\SYSTEM32\WBEM;C:\WINDOWS\SYSTEM32\WINDOWSPOWERSHELL\V1.0;C:\PROGRAM FILES (X86)\SKYPE\PHONE;C:\xampp\php;F:\PuTTY;C:\xamppp\php;C:\ProgramData\ComposerSetup\bin;C:\ProgramData\chocolatey\bin;C:\Program Files\Java\jdk1.8.0_152\bin;C:\Program Files (x86)\Yarn\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files (x86)\Microsoft VS Code\bin;E:\Git\cmd;E:\nodejs;C:\Users\makhm\AppData\Local\Microsoft\WindowsApps;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\makhm\AppData\Roaming\Composer\vendor\bin;C:\Users\makhm\AppData\Local\Yarn\bin;C:\Users\makhm\AppData\Roaming\npm;E:\Git\usr\bin\vendor_perl;E:\Git\usr\bin\core_perl
9 verbose lifecycle firstdesktopapp#1.0.0~start: CWD: E:\NodeJS Projects\ElectronJs\FirstDesktopAPp
10 silly lifecycle firstdesktopapp#1.0.0~start: Args: [ '/d /s /c', 'electron .' ]
11 silly lifecycle firstdesktopapp#1.0.0~start: Returned: code: 1 signal: null
12 info lifecycle firstdesktopapp#1.0.0~start: Failed to exec start script
13 verbose stack Error: firstdesktopapp#1.0.0 start: electron .
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (E:\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:182:13)
13 verbose stack at ChildProcess. (E:\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:182:13)
13 verbose stack at maybeClose (internal/child_process.js:962:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
14 verbose pkgid firstdesktopapp#1.0.0
15 verbose cwd E:\NodeJS Projects\ElectronJs\FirstDesktopAPp
16 verbose Windows_NT 10.0.17134
17 verbose argv "E:\nodejs\node.exe" "E:\nodejs\node_modules\npm\bin\npm-cli.js" "start"
18 verbose node v11.0.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error firstdesktopapp#1.0.0 start: electron .
22 error Exit status 1
23 error Failed at the firstdesktopapp#1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
"

I was using the latest version of nodejs 11 that's why that was not working when I install the 10.11 version it worked thanks for #pushkin.

Related

electron-build fails with ERR_ELECTRON_BUILDER_CANNOT_EXECUTE

goal
I want to build an electron app ON a windows Machine for a Rasperry PI 4 running Raspbian32
configuration
"linux": {
"target" : [
{
"target": "AppImage",
"arch": ["armv7l"]
}
]
},
calling
"build-dist-lin": "webpack --mode production && electron-builder -l --config .env.json",
returned ERROR
cannot get, wait error=Get
"https://service.electron.build/find-build-agent?no-cache=1ghlrte":
dial tcp 51.15.76.176:443: connectex: A connection attempt failed
because the connected party did not properly respond after a period of
time, or established connection failed because connected host has
failed to respond.
attempt=0
waitTime=2
Error: C:\A\Repo\test\node_modules\app-builder-bin\win\x64\app-builder.exe exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
No Leads
There is no further information in this log to know where then ... it goes wrong. In the same env.json I also have a Windows Configuration part which runs perfectly well with calling it with -w. So that means that the configuration is probably ok. And that means it fails somewhere else.
full log:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\A\\Tools\\nodejs\\node.exe',
1 verbose cli 'C:\\A\\Tools\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'build-dist-lin'
1 verbose cli ]
2 info using npm#6.13.4
3 info using node#v12.16.1
4 verbose run-script [ 'prebuild-dist-lin', 'build-dist-lin', 'postbuild-dist-lin' ]
5 info lifecycle testingtest#0.0.39~prebuild-dist-lin: testingtest#0.0.39
6 info lifecycle testingtest#0.0.39~build-dist-lin: testingtest#0.0.39
7 verbose lifecycle testingtest#0.0.39~build-dist-lin: unsafe-perm in lifecycle true
8 verbose lifecycle testingtest#0.0.39~build-dist-lin: PATH: C:\A\Tools\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\A\Repo\testingtestplayer\node_modules\.bin;C:\Python27\;C:\Python27\Scripts;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\WINDOWS\System32\OpenSSH\;C:\a\tools\nodejs\;C:\ProgramData\chocolatey\bin;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn\;C:\Program Files\Microsoft SQL Server\150\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files\dotnet\;C:\a\tools\Git\cmd;C:\Users\edward.deleau\AppData\Local\Microsoft\WindowsApps;C:\a\tools\Microsoft VS Code\bin;C:\Users\edward.deleau\AppData\Roaming\npm;C:\Users\edward.deleau\.dotnet\tools;C:\Users\edward.deleau\.dotnet\tools
9 verbose lifecycle testingtest#0.0.39~build-dist-lin: CWD: C:\A\Repo\testingtestplayer
10 silly lifecycle testingtest#0.0.39~build-dist-lin: Args: [
10 silly lifecycle '/d /s /c',
10 silly lifecycle 'webpack --mode production && electron-builder -l --config .env.json'
10 silly lifecycle ]
11 silly lifecycle testingtest#0.0.39~build-dist-lin: Returned: code: 1 signal: null
12 info lifecycle testingtest#0.0.39~build-dist-lin: Failed to exec build-dist-lin script
13 verbose stack Error: testingtest#0.0.39 build-dist-lin: `webpack --mode production && electron-builder -l --config .env.json`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\A\Tools\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:311:20)
13 verbose stack at ChildProcess.<anonymous> (C:\A\Tools\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:311:20)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid testingtest#0.0.39
15 verbose cwd C:\A\Repo\testingtestplayer
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\\A\\Tools\\nodejs\\node.exe" "C:\\A\\Tools\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build-dist-lin"
18 verbose node v12.16.1
19 verbose npm v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error testingtest#0.0.39 build-dist-lin: `webpack --mode production && electron-builder -l --config .env.json`
22 error Exit status 1
23 error Failed at the testingtest#0.0.39 build-dist-lin script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Seems to be an issue with the electron builder. Since the free service host associated with the electron builder is unavailable and there by it refuses the connection. You could monitor the issue thread from the below link. This issue has been watched along for a long time I believe.
https://github.com/electron-userland/electron-builder/issues/3569
Unfortunately it doesn't seem that such issue will be fixed anytime soon, as we can see from the amount of (mostly open) GitHub issues that have been opened from users that are trying to deal with such problem in the past months:
service.electron.build is unavailable
Error: Cannot get, wait error=Get https://service.electron.build/find-build-agent
service.electron.build is unavailable - Urgently please suggest an alternate
Local build service not detected
Unable to build AppImage on Windows - service.electron.build
Connection to remote builder refused, while building linux package
That said, I used the following workarond using Docker that made me able to build a Linux redistributable .deb package for my Electron App from Windows 10 in less than 5 minutes:
Install Docker (link)
Download the electronuserland/builder Docker image with the following console command:
docker pull electronuserland/builder
From the Electron project's root folder (such as C:\MyApp), type the following command-line command to run the container and map the Electron project's root folder to the /project virtual path:
docker run -rm -ti -v C:\MyApp\:/project -w /project electronuserland/builder
From inside the container, type the following commands to upgrade the Electron project's Yarn packages, globally install the electron-builder package and build the Linux redistributable package:
cd /project
yarn upgrade
yarn global add electron-builder
electron-builder -l
If everything went smooth, you should be able to locate your MyApp.deb file (or rpm, AppImage, or anything you've configured within the electron-builder's package.json file) inside the Electron project's /dist/ folder.
For further info about this whole procedure and a bit of background, check out this post on my blog.

Getting npm ERR! exited with error code: 128

I tried 'RNVectorIcons' package in my react native project using the following link react-native-vector-icons.I used pod install command in my terminal.But I got the following error in my terminal window.
Analyzing dependencies
Fetching podspec for `RNVectorIcons` from `../node_modules/react-native-vector-icons`
Downloading dependencies
Installing RNVectorIcons (4.6.0)
Installing React (0.11.0)
[!] /bin/bash -c
set -e
npm install --production
npm WARN deprecated connect#2.8.3: connect 2.x series is deprecated
npm WARN deprecated babel-core#5.8.21: Babel 5 is no longer being maintained. Upgrade to Babel 6.
npm WARN deprecated graceful-fs#3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated line-numbers#0.2.0: Copy its ~20 LOC directly into your code instead.
npm WARN deprecated tough-cookie#1.2.0: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated coffee-script#1.6.3: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated formatio#1.1.1: This package is unmaintained. Use #sinonjs/formatio instead
npm WARN deprecated gulp-util#3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t git://github.com/facebook/react.git
npm ERR!
npm ERR! undefined
npm ERR! exited with error code: 128
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/macmini1/.npm/_logs/2018-06-21T12_59_11_182Z-debug.log
my package.json file look like the following:
{
"name": "sample",
"version": "0.0.1",
"private": true,
"scripts": {
"gulp": "gulp"
},
"dependencies": {
"eslint": "4.19.1",
"eslint-config-airbnb": "16.1.0",
"eslint-config-airbnb-base": "12.1.0",
"eslint-config-rallycoding": "3.2.0",
"eslint-import-resolver-webpack": "0.10.0",
"eslint-plugin-import": "2.12.0",
"eslint-plugin-jsx-a11y": "6.0.3",
"eslint-plugin-react": "7.8.2",
"react": "16.3.1",
"react-native": "0.55.4",
"react-native-vector-icons": "4.6.0",
"react-navigation": "2.3.1"
},
"devDependencies": {
"babel-jest": "23.0.1",
"babel-preset-react-native": "4.0.0",
"jest": "23.1.0",
"react-test-renderer": "16.3.1"
},
"jest": {
"preset": "react-native"
}
debug.log file is
1609 verbose stack Error: exited with error code: 128
1609 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/util/finished.js:12:19)
1609 verbose stack at ChildProcess.emit (events.js:182:13)
1609 verbose stack at maybeClose (internal/child_process.js:961:16)
1609 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5)
1610 verbose cwd /Users/macmini1/Library/Caches/CocoaPods/Pods/Release/React/0.11.0-ab1a2
1611 verbose Darwin 17.0.0
1612 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--production"
1613 verbose node v10.4.1
1614 verbose npm v6.1.0
1615 error Error while executing:
1615 error /usr/bin/git ls-remote -h -t git://github.com/facebook/react.git
1615 error
1615 error undefined
1615 error exited with error code: 128
1616 verbose exit [ 1, true ]
How to solve this issue?
Could you provide the contents of the debug log? Did you only experience this issue since adding this package?
Can you also post the content of your package.json file?
Do also please have look at this question/solution, it does seem like the problem you're having: react-native init AwesomeProject unable to connect to github.com
Update
It could be related to the way github is being accessed. Could you try running the following command before trying it again?
git config --global url."https://".insteadOf git://

environment setup for hyperledger composer "npm install -g generator-hyperledger-composer"?

need step by step tutorials ?
I get the below error. Do i need to install dot net?
102024 verbose lifecycle hashtable#2.0.2~install: unsafe-perm in lifecycle true
102025 verbose lifecycle hashtable#2.0.2~install: PATH: C:\Users\Mabel\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Users\Mabel\AppData\Roaming\npm\node_modules\generator-hyperledger-composer\node_modules\hashtable\node_modules.bin;C:\Users\Mabel\AppData\Roaming\npm\node_modules\generator-hyperledger-composer\node_modules.bin;C:\Users\Mabel\AppData\Roaming\npm\node_modules.bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;E:\project\Maven\maven-2.2.1\bin;C:\Program Files\Java\jdk1.8.0_20\bin;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\Git\cmd;C:\Go\bin;C:\Windows\System32\cmd.exe;C:\Program Files\nodejs\;C:\Program Files\Docker Toolbox;C:\Users\Mabel\AppData\Roaming\npm;C:\Program Files (x86)\Microsoft VS Code\bin
102026 verbose lifecycle hashtable#2.0.2~install: CWD: C:\Users\Mabel\AppData\Roaming\npm\node_modules\generator-hyperledger-composer\node_modules\hashtable
102027 silly lifecycle hashtable#2.0.2~install: Args: [ '/d /s /c', 'node-gyp configure build' ]
102028 silly lifecycle hashtable#2.0.2~install: Returned: code: 1 signal: null
102029 info lifecycle hashtable#2.0.2~install: Failed to exec install script
102030 verbose unlock done using C:\Users\Mabel\AppData\Roaming\npm-cache_locks\staging-021d018a547f4a2b.lock for C:\Users\Mabel\AppData\Roaming\npm\node_modules.staging
102031 silly rollbackFailedOptional Starting
102032 silly rollbackFailedOptional Finishing
102033 silly runTopLevelLifecycles Finishing
102034 silly install printInstalled
102035 verbose stack Error: hashtable#2.0.2 install: node-gyp configure build
102035 verbose stack Exit status 1
102035 verbose stack at EventEmitter. (C:\Users\Mabel\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:255:16)
102035 verbose stack at emitTwo (events.js:106:13)
102035 verbose stack at EventEmitter.emit (events.js:191:7)
102035 verbose stack at ChildProcess. (C:\Users\Mabel\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14)
102035 verbose stack at emitTwo (events.js:106:13)
102035 verbose stack at ChildProcess.emit (events.js:191:7)
102035 verbose stack at maybeClose (internal/child_process.js:877:16)
102035 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
102036 verbose pkgid hashtable#2.0.2
102037 verbose cwd C:\Windows\system32
102038 error Windows_NT 6.1.7601
102039 error argv "C:\Program Files\nodejs\node.exe" "C:\Users\Mabel\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install" "-g" "generator-hyperledger-composer"
102040 error node v6.10.0
102041 error npm v3.10.10
102042 error code ELIFECYCLE
102043 error hashtable#2.0.2 install: node-gyp configure build
102043 error Exit status 1
102044 error Failed at the hashtable#2.0.2 install script 'node-gyp configure build'.
102044 error Make sure you have the latest version of node.js and npm installed.
102044 error If you do, this is most likely a problem with the hashtable package,
102044 error not with npm itself.
102044 error Tell the author that this fails on your system:
102044 error node-gyp configure build
102044 error You can get information on how to open an issue for this project with:
102044 error npm bugs hashtable
102044 error Or if that isn't available, you can get their info via:
102044 error npm owner ls hashtable
102044 error There is likely additional logging output above.
102045 verbose exit [ 1, true ]
Unfortunately Hyperledger Composer is not supported on Windows and although possible to make some progress in getting it working, it is not a trivial exercise.
I would recommend installing something like virtual box and then creating a VM to run a full linux distribution such as Ubuntu.
The official Documentation (See here) is the best place to learn composer. Hyperledger is a big community comprising of many projects (Read here). I have also received hashtable error. I made a workaround by first doing npm install -g hashtable#2.0.2 and then npm install -g of the composer packages.

ionic build ios --release failed

I'm newer here and i would like a help from you. My english is not very well, but i'm trying to explain my issue.
When i run the ionic build ios --release on my ionic app, and the temrinal shows the below error:
ionic build ios --release
Running 'build:before' npm script before build
> ionic-hello-world# build /Users/allanbarbosa/Projetos/mobi-unidadedigital/v3
> ionic-app-scripts build
[15:37:26] ionic-app-scripts 0.0.28
[15:37:26] build prod started ...
[15:37:26] clean started ...
[15:37:27] clean finished in 62 ms
[15:37:27] copy started ...
[15:37:27] ngc started ...
[15:37:27] lint started ...
[15:37:27] copy finished in 593 ms
[15:37:32] lint finished in 5.18 s
[15:37:51] ngc error: Error: Error at /Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/.tmp/pages/ConsultantChat/consultant-chat.ngfactory.ts:432:42: Property 'cleanFilter' does not exist on type 'ConsultantChat'.
Error at /Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/.tmp/pages/Estatisticas/components/PointsResume/points-resume.ngfactory.ts:552:40: Property 'accordeon' is private and only accessible within class 'PointsResume'.
Error at /Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/.tmp/pages/Estatisticas/components/PointsResume/points-resume.ngfactory.ts:557:40: Property 'animaAccordeon' is private and only accessible within class 'PointsResume'.
Error at /Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/.tmp/pages/Estatisticas/components/PointsResume/points-resume.ngfactory.ts:562:40: Property 'accordeon' is private and only accessible within class 'PointsResume'.
Error at /Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/.tmp/pages/Estatisticas/components/PointsResume/points-resume.ngfactory.ts:567:45: Property 'accordeon' is private and only accessible within class 'PointsResume'.
Error at /Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/.tmp/pages/Estatisticas/estatistica.ngfactory.ts:552:42: Property 'ConsultantChat' does not exist on type 'EstatisticaPage'.
Error at /Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/.tmp/pages/ModalAccount/modal-account.ngfactory.ts:325:29: Supplied parameters do not match any signature of call target.
at check (/Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/node_modules/#angular/tsc-wrapped/src/tsc.js:31:15)
at Tsc.typeCheck (/Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/node_modules/#angular/tsc-wrapped/src/tsc.js:86:9)
at /Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/node_modules/#angular/tsc-wrapped/src/main.js:33:23
at process._tickCallback (internal/process/next_tick.js:103:7)
at Function.Module.runMain (module.js:577:11)
at startup (node.js:160:18)
at node.js:456:3
[15:37:51] ngc error: Compilation failed
[15:37:51] ngc failed: NGC encountered an error
[15:37:51] Error: NGC encountered an error
at ChildProcess.<anonymous> (/Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/node_modules/#ionic/app-scripts/dist/ngc.js:60:24)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:852:16)
at Socket.<anonymous> (internal/child_process.js:323:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at Pipe._handle.close [as _onclose] (net.js:492:12)
Error running ionic app script "build": Error: NGC encountered an error
npm
ERR! Darwin 16.1.0
npm
ERR! argv "/usr/local/Cellar/node/6.2.1/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR!
node v6.2.1
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR!
ionic-hello-world# build: `ionic-app-scripts build`
npm ERR!
Exit status 1
npm ERR!
npm ERR!
Failed at the ionic-hello-world# build script 'ionic-app-scripts build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ionic-hello-world package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! ionic-app-scripts build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs ionic-hello-world
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls ionic-hello-world
npm
ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!
/Users/allanbarbosa/Projetos/mobi-unidadedigital/v3/npm-debug.log
Caught exception:
undefined
I trying to search on my pages this ngc problems, but no successful. Someone can help me?
My ionic info
Your system information:
Cordova CLI: 6.4.0
Gulp version: CLI version 3.9.1
Gulp local:
Ionic Framework Version: 2.0.0-rc.0
Ionic CLI Version: 2.1.0
Ionic App Lib Version: 2.1.0-beta.1
ios-deploy version: 1.9.0
ios-sim version: 5.0.8
OS: Mac OS X El Capitan
Node Version: v6.2.1
Xcode version: Xcode 8.1 Build version 8B62

React Native iOS Deployment Error

The below error occurred while in attempt to deploy my app to the mobile phone for testing.
the app function in the Xcode Simulator, and was able to export to the app into iPhone for testing.
after running the npm start the following error occurred.
while the iPhone app did load but count not connect to development server due to not able to npm start.
And yes both the iPhone and my computer is on the same wireless network.
┌────────────────────────────────────────────────────────────────────────────┐
│ Running packager on port 8081. │
│ │
│ Keep this packager running while developing on any JS projects. Feel │
│ free to close this tab and run your own packager instance if you │
│ prefer. │
│ │
│ https://github.com/facebook/react-native │
│ │
└────────────────────────────────────────────────────────────────────────────┘
Looking for JS files in
/Users/jimmylin/dev/ga/WalkingTour/SohoDuck
[10:40:02 AM] <START> Building Dependency Graph
[10:40:02 AM] <START> Crawling File System
[Hot Module Replacement] Server listening on /hot
React packager ready.
ERROR: Unknown option --no-pretty
ERROR: Unknown option --no-pretty
Watchman: watchman--no-pretty get-sockname returned with exit code 1 ERROR: Unknown option --no-pretty
ERROR watchman--no-pretty get-sockname returned with exit code 1 ERROR: Unknown option --no-pretty
Error: watchman--no-pretty get-sockname returned with exit code 1 ERROR: Unknown option --no-pretty
at ChildProcess.<anonymous> (/Users/jimmylin/dev/ga/WalkingTour/SohoDuck/node_modules/fb-watchman/index.js:198:18)
at emitTwo (events.js:100:13)
at ChildProcess.emit (events.js:185:7)
at maybeClose (internal/child_process.js:850:16)
at Socket.<anonymous> (internal/child_process.js:323:11)
at emitOne (events.js:90:13)
at Socket.emit (events.js:182:7)
at Pipe._onclose (net.js:477:12)
See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.
npm ERR! Darwin 15.3.0
npm ERR! argv "/usr/local/Cellar/node/5.9.1/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v5.9.1
npm ERR! npm v3.7.3
npm ERR! code ELIFECYCLE
npm ERR! SohoDuck#0.0.1 start: `node node_modules/react-native/local-cli/cli.js start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the SohoDuck#0.0.1 start script 'node node_modules/react-native/local-cli/cli.js start'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the SohoDuck package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node node_modules/react-native/local-cli/cli.js start
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs SohoDuck
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls SohoDuck
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/jimmylin/dev/ga/WalkingTour/SohoDuck/npm-debug.log
any suggestion would be greatly appreciated.
Correct installation of dependencies
Uninstall watchman and flow via npm and homebrew
Install watchman and flow only via homebrew
brew install watchman
brew install flow

Resources