electron/spec/fixtures/api/singleton/main.js

const { app } = require('electron');

app.whenReady().then(() => {
  console.log('started'); // ping parent
});

const gotTheLock = app.requestSingleInstanceLock();

app.on('second-instance', (event, args, workingDirectory) => {
  setImmediate(() => {
    console.log(JSON.stringify(args), workingDirectory);
    app.exit(0);
  });
});

if (!gotTheLock) {
  app.exit(1);
}
chore: update to standard 12 2018-09-14 02:10:51 +10:00			`const { app } = require('electron');`
spec: Add test case for app.makeSingleInstance 2017-09-20 11:58:10 +09:00
refactor: prefer using app.whenReady() (#21972) * docs: add references to app.whenReady() in isReady * refactor: prefer app.whenReady() In the docs, specs, and lib, replace instances of `app.once('ready')` (seen occasionally) and `app.on('ready')` (extremely common) with `app.whenReady()`. It's better to encourage users to use whenReady(): 1. it handles the edge case of registering for 'ready' after it's fired 2. it avoids the minor wart of leaving an active listener alive for an event that wll never fire again 2020-02-03 16:43:22 -06:00			`app.whenReady().then(() => {`
chore: update to standard 12 2018-09-14 02:10:51 +10:00			`console.log('started'); // ping parent`
Exit gracefully on linux (#12139) * Fix timing issue in singleton fixture. Singleton now sends the "we've started" message out only after it's received a `'ready'` event from `app`. Previously it sent the message out immediately, resulting in the parent test trying to manipulate it before Singleton's event loop was fully bootstrapped. * Check for graceful exits on Linux, too. Rewrite the "exits gracefully on macos" spec to run on Linux too. * Check for graceful exits everywhere. * Tweak comment * Better error logging in api-app-spec.js. (#12122) In the 'exits gracefully' test for app.exit(exitCode), print the relevant error information if the test fails. * Run the exit-gracefully test on macOS and Linux. Windows does not support sending signals, but Node.js offers some emulation with process.kill(), and subprocess.kill(). Sending signal 0 can be used to test for the existence of a process. Sending SIGINT, SIGTERM, and SIGKILL cause the unconditional termination of the target process. So, we'll need a different approach if we want to test this in win32. 2018-03-07 12:01:17 +09:00			`});`
spec: Add test case for app.makeSingleInstance 2017-09-20 11:58:10 +09:00
feat: new makeSingleInstance API (#12782) * Refactor app.makeSingleInstance * new API `app.isPrimaryInstance()` * new API `app.isSingleInstance()` * new event `app.on('second-instance')` * deprecated old syntax `app.makeSingleInstance(cb)` * deprecated old syntax of `app.makeSingleInstance() --> bool` in favor of `app.isPrimaryInstance()` * Fix spec, we don't need process.nextTick hacks any more * Make deprecation TODO for the return value of makeSingleInstance * Refactor makeSingleInstance to requestSingleInstanceLock and add appropriate deprecation comments * I swear this isn't tricking the linter * Make const * Add deprecation warnings for release, and add to planned-breaking-changes BREAKING CHANGE 2018-05-08 01:29:18 +10:00			`const gotTheLock = app.requestSingleInstanceLock();`

fix: second-instance additionalData parameter (#31661) * test: second-instance additionalData parameter * Fix posix implementation 2021-11-04 01:14:09 -07:00			`app.on('second-instance', (event, args, workingDirectory) => {`
test: add test for second-instance event parameter (#16798) * test: add test for second-instance event parameter * robustify getting data from child process * fix test on windows * fix lint * Update api-app-spec.js * fix package-lock.json 2019-03-12 08:56:28 -07:00			`setImmediate(() => {`
chore: cleanup unusued variables + enable linting (#38898) 2023-06-26 11:51:54 +02:00			`console.log(JSON.stringify(args), workingDirectory);`
test: add test for second-instance event parameter (#16798) * test: add test for second-instance event parameter * robustify getting data from child process * fix test on windows * fix lint * Update api-app-spec.js * fix package-lock.json 2019-03-12 08:56:28 -07:00			`app.exit(0);`
			`});`
spec: Add test case for app.makeSingleInstance 2017-09-20 11:58:10 +09:00			`});`

feat: new makeSingleInstance API (#12782) * Refactor app.makeSingleInstance * new API `app.isPrimaryInstance()` * new API `app.isSingleInstance()` * new event `app.on('second-instance')` * deprecated old syntax `app.makeSingleInstance(cb)` * deprecated old syntax of `app.makeSingleInstance() --> bool` in favor of `app.isPrimaryInstance()` * Fix spec, we don't need process.nextTick hacks any more * Make deprecation TODO for the return value of makeSingleInstance * Refactor makeSingleInstance to requestSingleInstanceLock and add appropriate deprecation comments * I swear this isn't tricking the linter * Make const * Add deprecation warnings for release, and add to planned-breaking-changes BREAKING CHANGE 2018-05-08 01:29:18 +10:00			`if (!gotTheLock) {`
spec: Add test case for app.makeSingleInstance 2017-09-20 11:58:10 +09:00			`app.exit(1);`
			`}`