unsupported flag --disable-setuid-sandbox

I suggest removing this code, the flag is no longer used in chrome.

if (process.platform === 'linux') {
           flags.push('--disable-setuid-sandbox');
        }

[patrickhulce]

This flag is still in use in the Chromium codebase AFAICT, so we would like to continue supporting it, but we’ve added ignoreDefaultFlags as a way to disable other default flags in chrome-launcher that doesn’t yet affect this one.

If anyone would like to submit a PR that adds a check for ignoreDefaultFlags to https://github.com/GoogleChrome/chrome-launcher/blob/e67a10dffccd1d7509d671145b0b4ee368e34528/src/chrome-launcher.ts#L150-L152

I think that sounds good! 👍

[JavaScriptDude]

I have found a workaround for this on Linux.

You can use the ignoreDefaultFlags setting as follows:

const ChromeLauncher = require('chrome-launcher');

var flags = ChromeLauncher.Launcher.defaultFlags();

// optional: filter out flags
// Eg. Enabling extensions and Audio
// flags = flags.filter(flag => flag !== '--disable-extensions' && flag !== '--mute-audio')

// optional: Add you own flags
// flags.push('--proxy-server=192.168.101.200:8213')

ChromeLauncher.launch({
   startingUrl: ''
  ,userDataDir: '/dpool/vcmain/sys/chrome/profiles/CORP_DEV_LOCAL'
  ,ignoreDefaultFlags: true
  ,chromeFlags: flags
}).then(chrome => {
  console.log(`Chrome debugging port running on ${chrome.port}`);
});