Oliver Medhurst

Use `require.main.filename` as basis, with a central `gluon_data` (?) directory with subdirs for Chromium/Firefox (not per browser, just per type?),

See spec PR: https://github.com/tc39/proposal-array-grouping/pull/47 - `Array.prototype.group` -> `Object.groupBy` - `Array.prototype.groupToMap` -> `Map.groupBy`

See spec PR: https://github.com/tc39/proposal-intl-locale-info/pull/67 - `get Intl.Locale.prototype.calendars` -> `Intl.Locale.prototype.getCalendars()` - etc (see PR)

feat: use simpler env vars for win32

4

Just use environment variables `PROCESSOR_ARCHITEW6432`/`PROCESSOR_ARCHITECTURE` on win32 instead of checking paths. Closes #26. Bonus when running as x86: probably much faster and works with no IO access. Also ~10% smaller...

This seems a lot simpler and should work just as well?

Closes #276 by adding a new option (`"global": true`) to avoid possible breaking changes.

`url.parse` is deprecated, `new URL` is supported since Node v10.

- `needle` -> built-in `fetch`? - Remove `lodash`? (only being used for `_.uniq`)

Add a basic ignore subpaths argument. just checks if paths include it, no regex/glob/etc yet. Closes #102.

Comments on WinterCG CLI API proposal?

3

Hi Node TSCers, I recently started a [CLI API WinterCG proposal](https://github.com/CanadaHonk/proposal-cli-api). This proposes to add a common API between runtimes for CLI functionality, most notably arguments and environment variables (plus...