devtron | Tool integration platform for Kubernetes | Continuous Deployment library

I Know that there is a lot of topic about this, but since none of them work, I must make a new one, I'm quite confused as why my electron app doesn't launch when I used yarn dev for my project, but when my friends try it, in his laptop, he can run and the apps launch normally without any problem, so Is there anyone here ever face the same problem with me? if there is someone, how can you solve this problem?

this is what my terminal looks like:

for information I used:

I do have a JavaScript code snippet that iterates through an array of fields looking for specific properties and adding those to a dictionary. Also, see this site for another example.

After updating all my outdated npm packages to @latest, my electron app fails to start, giving the error

ERROR in ./src/index.js [0] Module build failed (from ./node_modules/babel-loader/lib/index.js): [0] Error: Plugin/Preset files are not allowed to export objects, only functions. In /Users/nyxynyx/foobar/node_modules/babel-preset-stage-0/lib/index.js

Any idea what went wrong? Thank you everyone!

.babelrc

I'm trying to use the bcrypt-package inside a vue-electron project, but there is an N-api version issue when I try to run it:

I have installed the template from Electron-vue and I'm experiencing an issue with specific websites. These websites work on Chrome and Edge, yet, fail to completely load in webview.

The following example is the whole setup of the view. The console of this show that Local Storage, Session Storage and IndexedDB only have an entry for the website faselhd but have no data inside. The Cookies has an entry for the website with this type of data fcuid

Hi I am developing an Electron-react app using create-react-app boilerplate and electron-builder to package and deploy it.

However, on running electron-builder using yarn in the CL it shows this error.

As many other people have had the same issue, I'm struggling to interact with a element to change routes and render a new component. I am able to click on the link and the path for my application changes in my redux store, but no component gets updated. My root component does not seem to respond to shouldComponentUpdate, even though props are changing and the full setup is similar to how connected-react-router describes it needs to be.

To test

The sample code (git repo) is a MVP (minimum viable product) - it can easily replicate the problem I am seeing.

I recently set up a new project based on https://electron-react-boilerplate.js.org. This worked fine for a little bit, then I decided to start over again and re-cloned the electron-react-boilerplate Git repo to a new directory and deleted the old one.

Now when I run yarn run dev in the new project directory, I get a strange error:

Reading /Users/myuser/Code/OLD_PROJECT_NAME/node_modules/devtron/manifest.json failed. Error: ENOENT: no such file or directory, open '/Users/myuser/Code/OLD_PROJECT_NAME/node_modules/devtron/manifest.json' at Object.fs.openSync (fs.js:577:3) at Object.module.(anonymous function) [as openSync] (ELECTRON_ASAR.js:166:20) at Object.fs.readFileSync (fs.js:483:33) at Object.fs.readFileSync (ELECTRON_ASAR.js:563:29) at getManifestFromPath (/Users/myuser/Code/NEW_PROJECT_NAME/node_modules/electron/dist/Electron.app/Contents/Resources/electron.asar/browser/chrome-extension.js:30:26) at Function.BrowserWindow.addExtension (/Users/myuser/Code/NEW_PROJECT_NAME/node_modules/electron/dist/Electron.app/Contents/Resources/electron.asar/browser/chrome-extension.js:362:22) at Function.BrowserWindow.addDevToolsExtension (/Users/myuser/Code/NEW_PROJECT_NAME/node_modules/electron/dist/Electron.app/Contents/Resources/electron.asar/browser/chrome-extension.js:394:40) at App. (/Users/myuser/Code/NEW_PROJECT_NAME/node_modules/electron/dist/Electron.app/Contents/Resources/electron.asar/browser/chrome-extension.js:423:23) at Object.onceWrapper (events.js:273:13) at App.emit (events.js:187:15)

Note that for some reason, it tries to read the manifest.json file from the old project directory which doesn't even exist anymore. I've grepped the entire new directory for occurrences of the old project name hunting down what could be wrong but nothing comes out of it.

I've tried removing node_modules, didn't help.

I also tried running yarn cache clean but that didn't help either.

Where could it possibly be getting the old project directory from?

I'm on macOS Mojave with Node 11.4.0.

I have an angular app which has been converted into a desktop app using the electron-builder. Now, I am trying to implement the auto-updates features into it. I don't want electron-builder to publish the changes to the github repository. (Note: The whole app is on a private github repo.) I want to manually upload the necessary .dmg, .zip, .yml files to the release tag and I want that to be picked up by the auto updater. How can I achieve this?

Currently, I have the source .zip and .tar.gz as part of my release tag. And whenever I try to invoke the autoUpdater.checkForUpdates() when the app is ready, I get the following error saying: