Can't launch firefox

I tried with 2.1.0 but it doesn’t work.

  const browser = await puppeteer.launch({'headless': false, 'product': 'firefox'})

From Puppeteer v2.1.0 onwards, as an experimental feature, you can specify puppeteer.launch({product: ‘firefox’}) to run your Puppeteer scripts in Firefox, without any additional custom patches.

[mjzffr]

wait-for-browser is a Firefox argument relevant to Windows. This might relevant to #5673

In the meantime, you can include wait-for-browser in the args option of Puppeteer.launch

[Sue9445]

const puppeteer = require('puppeteer');
(async () => {
          const browser = await puppeteer.launch({
                 'headless': false, 'product': 'firefox',
                  'executablePath': "C:\\Program Files\\Mozilla Firefox\\firefox.exe
          });
          const page = await browser.newPage();
})();

(node:23104) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process!

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md

at onClose (C:\sources\test2\New folder\node_modules\puppeteer\lib\Launcher.js:751:14)
at ChildProcess.<anonymous> (C:\sources\test2\New folder\node_modules\puppeteer\lib\Launcher.js:741:61)
at ChildProcess.emit (events.js:215:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)

(node:23104) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:23104) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. [Error: EBUSY: resource busy or locked, unlink ‘C:\Users\meoti\AppData\Local\Temp\puppeteer_dev_firefox_profile-5ijv8F\key4.db’] { errno: -4082, code: ‘EBUSY’, syscall: ‘unlink’, path: ‘C:\Users\meoti\AppData\Local\Temp\puppeteer_dev_firefox_profile-5ijv8F\key4.db’

I solved this error by adding the “-wait-for-browser” arg.