Remove Warning On New Headless Setting

[tmcconechy]

Remove Warning On New Headless Setting

[colinrotherham]

If you set { headless: 1 } instead of { headless: true } it will bypass the deprecation check

[colinrotherham]

Setting { headless: 'new' } switches to "new headless" which will be the default in future

Chrome’s Headless mode gets an upgrade: introducing --headless=new
https://developer.chrome.com/articles/new-headless/

const browser = await puppeteer.launch({
  headless: 'new',
  // `headless: true` (default) enables old Headless;
  // `headless: 'new'` enables new Headless;
  // `headless: false` enables “headful” mode.
});

You should see Chrome icons in the Dock on macOS but the windows are invisible. Unlike "old headless" it can now run browser extensions but you'll likely see a drop in performance but they're aware of it (approx 30% slower)

[tmcconechy]

Thanks @colinrotherham that works. The warning was rather annoying as we see it flood our console

[gregberge]

Just use headless: "new". I made a new release and I updated the README to specify it.

[tmcconechy]

@gregberge headless: 'new" causes it to not be headless so get tons of browser windows. Is that correct? Whats the opposite of new. Unclear why they changed this to me seems unclear.