Giter Site home page Giter Site logo

desktop's Introduction

Create React App for the desktop with Electron

https://create-react-app.dev/docs/getting-started

Build Status

Appveyor Build Status

Note:

env files only for react

dot env files have no impact on the main electron process (yet). https://create-react-app.dev/docs/adding-custom-environment-variables/

this repo is an instantiated unejected create-react-app

Update CRA

  • remove src and public
  • run npx create-react-app recreate-cra-desktop --use-npm
  • move recreate-cra-desktop/src and recreate-cra-desktop/public to ./

ORG Readme

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

npm run build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify

desktop's People

Contributors

dependabot-preview[bot] avatar dependabot[bot] avatar greenkeeper[bot] avatar thisconnect avatar

Stargazers

avatar

Watchers

avatar avatar avatar

desktop's Issues

An in-range update of react-scripts is breaking the build 🚨

Version 1.0.15 of react-scripts was just published.

Branch Build failing 🚨
Dependency react-scripts
Current Version 1.0.14
Type devDependency

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

react-scripts 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • ❌ ci/circleci Your tests failed on CircleCI Details
Release Notes v1.0.15

1.0.15 (October 30, 2017)

🐛 Bug Fix

  • react-scripts

  • react-dev-utils, react-scripts

    • #3230 Fix watching for changes in src/node_modules. (@xjlim)

💅 Enhancement

  • react-scripts

  • babel-preset-react-app, react-dev-utils, react-error-overlay, react-scripts

  • react-dev-utils, react-error-overlay

  • create-react-app

    • #3355 Add preflight CWD check for npm to detect bad Windows setups. (@gaearon)

📝 Documentation

🏠 Internal

  • Other

  • react-error-overlay

    • #3122 Fix for add .gitattributes file #3080. (@ijajmulani)
    • #3267 Use production React version for bundled overlay. (@Timer)
    • #3264 Add warning when using react-error-overlay in production. (@Timer)
    • #3263 react-error-overlay has no dependencies now (it's bundled). (@Timer)
    • #3142 Make error overlay run in the context of the iframe. (@tharakawj)

  • react-scripts

    • #3150 Remove an useless negation in registerServiceWorker.js. (@dunglas)
    • #3158 Remove output.path from dev webpack config. (@nikolas)
    • #3281 Add a workaround for Uglify incompatiblity with Safari 10.0 in the future. (@satyavh)
    • #3146 Fix reason-react support. (@lpalmes)
    • #3236 Update style-loader and disable inclusion of its HMR code in builds. (@insin)
    • #3246 Update url-loader to 0.6.2 for mime ReDoS vulnerability. (@d3viant0ne)
    • #2914 <!doctype html> -> <!DOCTYPE html>. (@Hurtak)

Committers: 24

Migrating from 1.0.14 to 1.0.15

Inside any created project that has not been ejected, run:

npm install --save --save-exact [email protected]

or

yarn add --exact [email protected]
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of react-scripts is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.1.3 of react-scripts was just published.

Branch Build failing 🚨
Dependency react-scripts
Current Version 1.1.2
Type devDependency

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

react-scripts 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.

Status Details
  • ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
  • ❌ ci/circleci Your tests failed on CircleCI Details
Release Notes v1.1.3

1.1.3 (April 3, 2018)

🐛 Bug Fix

  • react-scripts

    • #4247 Fix environment.dispose is not a function error caused by a Jest bug. (@gaearon)

Committers: 1

Migrating from 1.1.2 to 1.1.3

Inside any created project that has not been ejected, run:

npm install --save --save-exact [email protected]

or

yarn add --exact [email protected]
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

Version 4.1.0 of eslint just got published.

Branch Build failing 🚨
Dependency eslint
Current Version 4.0.0
Type devDependency

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

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • ❌ ci/circleci Your tests failed on CircleCI Details
  • ✅ bitHound - Code No failing files. Details
  • ✅ bitHound - Dependencies No failing dependencies. Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes v4.1.0
  • e8f1362 Docs: Remove wrong descriptions in padded-block rule (#8783) (Plusb Preco)
  • 291a783 Update: enforceForArrowConditionals to no-extra-parens (fixes #6196) (#8439) (Evilebot Tnawi)
  • a21dd32 New: Add overrides/files options for glob-based config (fixes #3611) (#8081) (Sylvan Mably)
  • 879688c Update: Add ignoreComments option to no-trailing-spaces (#8061) (Jake Roussel)
  • b58ae2e Chore: Only instantiate fileEntryCache when cache flage set (perf) (#8763) (Gyandeep Singh)
  • 9851288 Update: fix indent errors on multiline destructure (fixes #8729) (#8756) (Victor Hom)
  • 3608f06 Docs: Increase visibility of code of conduct (fixes #8758) (#8764) (Kai Cataldo)
  • 673a58b Update: support multiple fixes in a report (fixes #7348) (#8101) (Toru Nagashima)
  • 7a1bc38 Fix: don't pass default parserOptions to custom parsers (fixes #8744) (#8745) (Teddy Katz)
  • c5b4052 Chore: enable computed-property-spacing on ESLint codebase (#8760) (Teddy Katz)
  • 3419f64 Docs: describe how to use formatters on the formatter demo page (#8754) (Teddy Katz)
  • a3ff8f2 Chore: combine tests in tests/lib/eslint.js and tests/lib/linter.js (#8746) (Teddy Katz)
  • b7cc1e6 Fix: Space-infix-ops should ignore type annotations in TypeScript (#8341) (Reyad Attiyat)
  • 46e73ee Fix: eslint --init installs wrong dependencies of popular styles (fixes #7338) (#8713) (Toru Nagashima)
  • a82361b Chore: Prevent package-lock.json files from being created (fixes #8742) (#8747) (Teddy Katz)
  • 5f81a68 New: Add eslintIgnore support to package.json (fixes #8458) (#8690) (Victor Hom)
  • b5a70b4 Update: fix multiline binary operator/parentheses indentation (#8719) (Teddy Katz)
  • ab8b016 Update: fix MemberExpression indentation with "off" option (fixes #8721) (#8724) (Teddy Katz)
  • eb5d12c Update: Add Fixer method to Linter API (#8631) (Gyandeep Singh)
  • 26a2daa Chore: Cache fs reads in ignored-paths (fixes #8363) (#8706) (Victor Hom)
Commits

The new version differs by 22 commits.

  • 7d9e3be 4.1.0
  • e727b7b Build: changelog update for 4.1.0
  • e8f1362 Docs: Remove wrong descriptions in padded-block rule (#8783)
  • 291a783 Update: enforceForArrowConditionals to no-extra-parens (fixes #6196) (#8439)
  • a21dd32 New: Add overrides/files options for glob-based config (fixes #3611) (#8081)
  • 879688c Update: Add ignoreComments option to no-trailing-spaces (#8061)
  • b58ae2e Chore: Only instantiate fileEntryCache when cache flage set (perf) (#8763)
  • 9851288 Update: fix indent errors on multiline destructure (fixes #8729) (#8756)
  • 3608f06 Docs: Increase visibility of code of conduct (fixes #8758) (#8764)
  • 673a58b Update: support multiple fixes in a report (fixes #7348) (#8101)
  • 7a1bc38 Fix: don't pass default parserOptions to custom parsers (fixes #8744) (#8745)
  • c5b4052 Chore: enable computed-property-spacing on ESLint codebase (#8760)
  • 3419f64 Docs: describe how to use formatters on the formatter demo page (#8754)
  • a3ff8f2 Chore: combine tests in tests/lib/eslint.js and tests/lib/linter.js (#8746)
  • b7cc1e6 Fix: Space-infix-ops should ignore type annotations in TypeScript (#8341)

There are 22 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of electron is breaking the build 🚨

The devDependency electron was updated from 3.0.0 to 3.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 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.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
  • ✅ ci/circleci: node-8: Your tests passed on CircleCI! (Details).
  • ❌ ci/circleci: node-6: Your tests failed on CircleCI (Details).
Release Notes for electron v3.0.1

Bug Fixes/Changes

  • chore: fix await in cleanup script (backport: 3-0-x). #14696

  • docs: specify BrowserWindow features passable to window.open. #14702

  • Fix second-instance handler signature. #14748

  • fix: do not set layer explicitly for frameless window. #14736

  • fix: actually return appmetrics. #14750

  • fix: initialize tracing controller before starting platform (3-0-x). #14503

  • docs: clarify allowable background colors for BrowserWindow transparency (backport: 3-0-x). #14781

  • fix: inconsistent titleBarStyle on transparent fullscreen. #14790

  • chore: bump libcc (3-0-x). #14809

  • fix: get background color from GtkMenuBar#menubar. #14812

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of electron-packager is breaking the build 🚨

Version 8.7.1 of electron-packager just got published.

Branch Build failing 🚨
Dependency electron-packager
Current Version 8.7.0
Type devDependency

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

As electron-packager is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • ❌ ci/circleci CircleCI is running your tests Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • ✅ bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 4 failing files. Details
Release Notes 8.7.1

Fixed

  • Usage docs for win32metadata.application-manifest and win32metadata.requested-execution-level
Commits

The new version differs by 9 commits.

  • f092a53 8.7.1
  • 6435a23 Travis: add stable branch to CI
  • 1f74734 Fix usage docs for requested-execution-level & application-manifest
  • 2e48d1d Merge pull request #664 from electron-userland/disable-node-8-osx
  • 4c9ec7f Force npm@4 for Node 8/OSX
  • 33794a1 Travis: Don't ignore Node 5/OSX builds anymore
  • 1b14e0b CI: test against Node 8
  • 52d5629 Update pkg-up to 2.x.x
  • b6fa6d7 Fix typo in NEWS

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of electron is breaking the build 🚨

Version 1.7.8 of electron just got published.

Branch Build failing 🚨
Dependency electron
Current Version 1.8.0
Type devDependency

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

As electron is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • ❌ ci/circleci Your tests failed on CircleCI Details
Release Notes electron v1.7.8

Bug Fixes

  • [SECURITY] Fixed Chromium RCE vulnerability

Linux

  • Fixed app.makeSingleInstance hanging. #10586

macOS

  • Fixed missing extension when saving a file without filters #10586
Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of react is breaking the build 🚨

Version 15.6.0 of react just got published.

Branch Build failing 🚨
Dependency react
Current Version 15.5.4
Type dependency

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

react is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • ✅ bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 4 failing files. Details
  • ✅ ci/circleci Your tests passed on CircleCI! Details
  • ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
Release Notes v15.6.0

15.6.0 (June 13, 2017)

React

  • Downgrade deprecation warnings to use console.warn instead of console.error. (@flarnie in #9753)
  • Add a deprecation warning for React.createClass. Points users to create-react-class instead. (@flarnie in #9771)
  • Add deprecation warnings and separate module for React.DOM factory helpers. (@nhunzaker in #8356)
  • Warn for deprecation of React.createMixin helper, which was never used. (@aweary in #8853)

React DOM

  • Add support for CSS variables in style attribute. (@aweary in #9302)
  • Add support for CSS Grid style properties. (@ericsakmar in #9185)
  • Fix bug where inputs mutated value on type conversion. (@nhunzaker in #9806)
  • Fix issues with onChange not firing properly for some inputs. (@jquense in #8575)
  • Fix bug where controlled number input mistakenly allowed period. (@nhunzaker in #9584)
  • Fix bug where performance entries were being cleared. (@chrisui in #9451)

React Addons

  • Fix AMD support for addons depending on react. (@flarnie in #9919)
  • Fix isMounted() to return true in componentWillUnmount. (@mridgway in #9638)
  • Fix react-addons-update to not depend on native Object.assign. (@gaearon in #9937)
  • Remove broken Google Closure Compiler annotation from create-react-class. (@gaearon in #9933)
  • Remove unnecessary dependency from react-linked-input. (@gaearon in #9766)
  • Point react-addons-(css-)transition-group to the new package. (@gaearon in #9937)
Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of electron is breaking the build 🚨

The devDependency electron was updated from 4.1.2 to 4.1.3.

🚨 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 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.

Status Details
  • ✅ ci/circleci: node-10: Your tests passed on CircleCI! (Details).
  • ✅ ci/circleci: node-8: Your tests passed on CircleCI! (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Release Notes for electron v4.1.3

Release Notes for v4.1.3

Fixes

  • Fixed IntersectionObserver.rootBounds for navigator zoom != 100%. #17583
  • Fixed app freeze when using custom stream protocol. #17267
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of electron-packager is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 11.1.0 of electron-packager was just published.

Branch Build failing 🚨
Dependency electron-packager
Current Version 11.0.1
Type devDependency

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

electron-packager 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • ❌ ci/circleci Your tests failed on CircleCI Details
Commits

The new version differs by 6 commits.

  • a02ccc0 11.1.0
  • a7437b9 Merge pull request #807 from malept/login-helper
  • c82cc36 Pre-download the MAS version being tested
  • 5852ebb Add support for customizing the login helper on MAS
  • cdd6709 Add more ESLint config
  • 5889db7 Upgrade eslint-config-standard to 11.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of react-dom is breaking the build 🚨

Version 15.6.0 of react-dom just got published.

Branch Build failing 🚨
Dependency react-dom
Current Version 15.5.4
Type dependency

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

react-dom is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • ✅ bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 4 failing files. Details
  • ✅ ci/circleci Your tests passed on CircleCI! Details
  • ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
Release Notes v15.6.0

15.6.0 (June 13, 2017)

React

  • Downgrade deprecation warnings to use console.warn instead of console.error. (@flarnie in #9753)
  • Add a deprecation warning for React.createClass. Points users to create-react-class instead. (@flarnie in #9771)
  • Add deprecation warnings and separate module for React.DOM factory helpers. (@nhunzaker in #8356)
  • Warn for deprecation of React.createMixin helper, which was never used. (@aweary in #8853)

React DOM

  • Add support for CSS variables in style attribute. (@aweary in #9302)
  • Add support for CSS Grid style properties. (@ericsakmar in #9185)
  • Fix bug where inputs mutated value on type conversion. (@nhunzaker in #9806)
  • Fix issues with onChange not firing properly for some inputs. (@jquense in #8575)
  • Fix bug where controlled number input mistakenly allowed period. (@nhunzaker in #9584)
  • Fix bug where performance entries were being cleared. (@chrisui in #9451)

React Addons

  • Fix AMD support for addons depending on react. (@flarnie in #9919)
  • Fix isMounted() to return true in componentWillUnmount. (@mridgway in #9638)
  • Fix react-addons-update to not depend on native Object.assign. (@gaearon in #9937)
  • Remove broken Google Closure Compiler annotation from create-react-class. (@gaearon in #9933)
  • Remove unnecessary dependency from react-linked-input. (@gaearon in #9766)
  • Point react-addons-(css-)transition-group to the new package. (@gaearon in #9937)
Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of react is breaking the build 🚨

There have been updates to the react monorepo:

    • The dependency react was updated from 16.7.0 to 16.8.0.
  • The dependency react-dom was updated from 16.7.0 to 16.8.0.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react 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.

Status Details
  • ❌ ci/circleci: node-10: Your tests failed on CircleCI (Details).
  • ❌ ci/circleci: node-8: Your tests failed on CircleCI (Details).
  • ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of react is breaking the build 🚨

There have been updates to the react monorepo:

    • The dependency react was updated from 16.5.2 to 16.6.0.
  • The dependency react-dom was updated from 16.5.2 to 16.6.0.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react 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.

Status Details
  • ✅ ci/circleci: node-8: Your tests passed on CircleCI! (Details).
  • ✅ ci/circleci: node-6: Your tests passed on CircleCI! (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of electron is breaking the build 🚨

The devDependency electron was updated from 4.0.3 to 4.0.4.

🚨 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 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.

Status Details
  • ❌ ci/circleci: node-8: CircleCI is running your tests (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
  • ❌ ci/circleci: node-10: Your tests failed on CircleCI (Details).
Release Notes for electron v4.0.4

Release Notes for v4.0.4

Features

  • Added getProcessMemoryInfo API. #16591

Fixes

  • Change the NODE_MODULE_VERSION to 69. #16687
  • Restored support for AES-CFB cipher, which was lost when switching from OpenSSL to BoringSSL. #16617
  • Restored support for RIPEMD160 digest, which was lost when switching from OpenSSL to BoringSSL. #16574

Documentation

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of electron is breaking the build 🚨

Version 1.6.7 of electron just got published.

Branch Build failing 🚨
Dependency electron
Current Version 1.6.9
Type devDependency

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

As electron is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • ✅ ci/circleci Your tests passed on CircleCI! Details,- ✅ continuous-integration/travis-ci/push The Travis CI build passed Details,- ❌ bitHound - Code 2 failing files. Details,- ✅ bitHound - Dependencies No failing dependencies. Details
Release Notes electron v1.6.7 beta

1.6.7 Release Notes

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of react is breaking the build 🚨

There have been updates to the react monorepo:

    • The dependency react was updated from 16.6.1 to 16.6.2.
  • The dependency react-dom was updated from 16.6.1 to 16.6.2.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react 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.

Status Details
  • ❌ ci/circleci: node-10: Your tests failed on CircleCI (Details).
  • ❌ ci/circleci: node-8: Your tests failed on CircleCI (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.