The devDependency @angular-devkit/build-angular was updated from 0.10.4 to 0.10.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/build-angular is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @angular-builders/custom-webpack was updated from 7.3.0 to 7.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-builders/custom-webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

As the title suggests, I'm not sure what to troubleshoot here.

80 error Windows_NT 6.1.7601
125 81 error argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Program Files     (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
126 82 error node v4.3.2
127 83 error npm  v2.14.12
128 84 error code ELIFECYCLE
129 85 error @ install: `node-gyp rebuild`
130 85 error Exit status 1
131 86 error Failed at the @ install script 'node-gyp rebuild'.
132 86 error This is most likely a problem with the  package,
133 86 error not with npm itself.
134 86 error Tell the author that this fails on your system:
135 86 error     node-gyp rebuild
136 86 error You can get their info via:
137 86 error     npm owner ls
138 86 error There is likely additional logging output above.
139 87 verbose exit [ 1, true ]

Add sections for debugging, running and testing the application

https://greenkeeper.io/

The devDependency @angular/cli was updated from 7.1.1 to 7.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @angular-devkit/build-angular was updated from 0.11.1 to 0.11.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/build-angular is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Using asar: false is not recommended - instead asar: true & asarUnpack shall be used

The dependency core-js was updated from 2.6.0 to 2.6.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

core-js is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Currently tests only titles

The dependency electron was updated from 4.0.7 to 4.0.8.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

electron is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency core-js was updated from 2.5.7 to 2.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

core-js is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency @angular-builders/custom-webpack was updated from 7.0.0 to 7.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-builders/custom-webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The issue is that use RouterModule after changes in the code are done the screen is white
@NgModule({ imports: [RouterModule.forRoot(routes, {useHash: true})], exports: [RouterModule] })

Also i had to change index.html base href tag to be empty:
<base href="">

The devDependency @types/node was updated from 10.12.3 to 10.12.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

@ install E:\Samples\Electron\electron-angular2-native
node-gyp rebuild

E:\Samples\Electron\electron-angular2-native>if not defined npm_config_node_gyp (node "E:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node rebuild )
'sed' is not recognized as an internal or external command,
operable program or batch file.
gyp: Call to 'find app/plugins/native -not -path ".//node_modules/" -mindepth 2 -name binding.gyp | sed -e s/$/:/' returned exit status 255. 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 (E:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:355:16)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Windows_NT 10.0.14393

The devDependency electron-reload was updated from 1.3.0 to 1.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

electron-reload is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency electron was updated from 3.0.12 to 3.0.13.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

electron is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

We have detected a problem with your Greenkeeper config file 🚨

Greenkeeper currently can’t work with your greenkeeper.json config file because it is invalid. We found the following issue:

1. The package path app.package.json in the group default is invalid. It must be a relative path to a package.json file. The path may not start with a slash, and it must end in package.json. Allowed characters for a path are alphanumeric, underscores, dashes, periods and the @ symbol (a-zA-Z_-.@).

Please correct this and commit the fix to your default branch (usually master). Greenkeeper will pick up your changes and try again. If in doubt, please consult the config documentation.

Here’s an example of a valid greenkeeper.json:

{
  groups: {
    frontend: {
      packages: [
        'webapp/package.json',
        'cms/package.json',
        'analytics/package.json'
      ]
    },
    build: {
      packages: [
        'package.json'
      ]
    }
  },
  ignore: [
    'standard',
    'eslint'
  ]
}

This files tells Greenkeeper to handle all dependency updates in two groups. All files in the frontend group will receive updates together, in one issue or PR, and the root-level package.json in the build group will be treated separately. In addition, Greenkeeper will never send updates for the standard and eslint packages.

🤖 🌴

The dependency electron was updated from 4.0.0 to 4.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

electron is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency @angular-devkit/build-angular was updated from 0.11.3 to 0.11.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/build-angular is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

First, great work on this project.

It doesn't seem that any external stylesheets are being applied. I have installed semantic-ui with NPM and have added the appropriate css file to the 'styles' array within the file webpack.config.dev.js. Things seem to be compiling correctly as my application loads but there are no styles are anything loaded.

entry: {
        main: [
            "./src/main.ts"
        ],
        polyfills: [
            "./src/polyfills.ts"
        ],
        styles: [
            "./node_modules/semantic-ui/dist/semantic.css",
            "./src/styles.scss"
        ]
    },

Is there an example you can provide to include external stylesheets or to even have the global styles working correctly? Maybe I am missing something simple.

Hi there, nice project! I'm trying to figure out how some things work in your project for better understanding 😄 I hope it's okay to post a question here 👼 .

When importing a node-module in your AppComponent, for example using the following line, it just works:
import * as fs from 'fs';

However, if I try to set up an Angular project manually that I can later open in electron, I am not able to compile, because I get the following error:
error TS2307: Cannot find module 'fs'.
What I did:
I created a simple new Angular 7 app + added a custom webpack config (listing 'fs' as external as in your webpack config) + updated angular.json to use that config (using @angular-builders/custom-webpack:browser and customWebpackConfig-option, exactly as you did). Then run ng build.
NOTE: @types/node and @angular-devkit/build-angular are installed and my editor (VSCode) is not showing any error.

Am I missing something? How do I get the ts-code compiled?

Best regards

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

electron-builder.yaml lists electronVersion as 3.0.7, should this be bumped to 4+?

The dependency electron was updated from 3.0.8 to 3.0.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

electron is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency @angular/cli was updated from 7.1.0 to 7.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Release Notes for v7.1.1

Commits

@ngtools/webpack (7.1.1)
Commit	Description	Notes
	files are not being updated when using `allowJs` or `resolveJsonModule` (#13089)	[Closes #13076] [Closes #12964]
	cleanup resources after modules are loaded (#12994)
@schematics/update (0.11.1)
Commit	Description	Notes
	replace environment variables in npm/yarn rc
@schematics/angular (7.1.1)
Commit	Description	Notes
	let tslint resolve codelyzer (#13101)	[Closes #13101] [Closes #13100]
	add providers into providers metadata but not inner Object with ut. (#13081)

---

Special Thanks

Alan Agius, Charles Lyding, Vikram Subramanian, 赵正阳, Hans Larsen, Mathou54, Krishna Mohan

Your Greenkeeper Bot 🌴

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

The devDependency karma was updated from 3.1.1 to 3.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

karma is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @angular/cli was updated from 7.3.0 to 7.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Release Notes for v7.3.1

Commits

@angular/cli (7.3.1)
Commit	Description	Notes
	Add an error message when we call `ng doc` without keyword. Currently, we open a page with the keyword `undefined`. (#13604)
	update terser-webpack-plugin (#13589)	[Closes #13582]
@schematics/angular (7.3.1)
Commit	Description	Notes
	update typescript to 3.2.4 (#13554)
	set cortrect file extention in config when using preprocessors (#13552)	[Closes #13550]
@angular-devkit/build-angular (0.13.1)
Commit	Description	Notes
	use sourcemap object in karma plugin (#13584)	[Closes #13580]
	remove deprecated `istanbul` from dependencies (#13567)	[Closes #13562]
	add missing open parenthesis in stacktrace (#13565)	[Closes #13558]
@angular-devkit/build-optimizer (0.13.1)
Commit	Description	Notes
	prefix renamed extended classes (#13613)	[Closes #13613] [Closes #11796]

---

Special Thanks

Filipe Silva, Alan Agius, Charles Lyding, Vikram Subramanian, William KOZA, Andrey Chalkin

Your Greenkeeper Bot 🌴

The devDependency electron-builder was updated from 20.36.0 to 20.36.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

electron-builder is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

simplelib shall reside in a different repository (as it is example for 3d party dependency) and the binary shall be added to this repo as a submodule. This will allow to create a separate CI build for simplelib.

node-ffi has not been in active development for a while and there are growing concerns about the future of the project. Would recommend to replace the package with more active repo node-ffi-napi.
This would also solve the node 9 support issue.

https://github.com/node-ffi-napi/node-ffi-napi

The devDependency electron-builder was updated from 20.38.2 to 20.38.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

electron-builder is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 11.9.0 to 11.9.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴