---
# System prepended metadata

title: Node.js Tooling Group Meeting 2020-06-12

---

# Node.js Tooling Group Meeting 2020-06-12

## Links

* **Recording**:
* **GitHub Issue**: 
* **Minutes Doc**: 

## Present

* Tooling team: @nodejs/tooling
* Darcy Clarke (@darcyclarke)
* Bradley Farias (@bmeck)
* Corey Farrell (@coreyfarrell)
* Ruy Adorno (@ruyadorno)
* Chris Hiller (@boneskull)
* Ian Sutherland (@iansu)

## Announcements

- let's do something for OpenJS Collab Summit
  - chris talk to jory?
 
## Agenda

* DEEP DIVE meeting proposals [#73](https://github.com/nodejs/tooling/issues/73)
* `fs` hooks [#63](https://github.com/nodejs/tooling/issues/63)
  * [proposed session](https://github.com/openjs-foundation/summit/issues/294) for a inter-WG group to look at this issue
  * Bradley: attendees should come with constraints (security, robustness, etc)
  * come prepared, gather thoughts, etc
  * Corey: #42 may fall under this
* chmod -R [#59](https://github.com/nodejs/tooling/issues/59)
  * Darcy looking at this, Ben helping
  * taking izs' implementation and node-ifying it
  * potential timing-based attack
  * Ben: chmodr is not nearly as popular as e.g., `mkdirp`
  * plan is to "vendor" like rimraf was done
  * (`chmodr` has no deps)
  * Ben: someone needs to deeply understand security implications, mitigations, etc.
  * Bradley: libuv may need to expose new API? `fd_opendir`. maybe can be mitigated w/ this using file descriptors instead of filenames.
  * sent the PR, then migrate to 'safer' version (later?)
* ESM module reloading and module graph [#51](https://github.com/nodejs/tooling/issues/51)
  * rename agenda item/issue to avoid "unloading" as this is not possible in V8
  * Chris & Ben meet to write down needs 
* Support for hooking spawn / spawnSync without patching. [#48](https://github.com/nodejs/tooling/issues/48)
  * *remove from agenda for now, but is still a need; see #63*
* A better way to detect a process is exiting [#42](https://github.com/nodejs/tooling/issues/42)
  * Bradley: could have a "non-removable" event listener??
  * alternative: async-hooks-api like thing; `let unsubscribe = listenForThing() ... call unsubscribe()`
  * Chris still has the action item which was to list all of the conditions in which this "event" should deal with
  * https://www.npmjs.com/package/signal-exit look at unit tests for list
* Source Map V3 Support in Node.js [#40](https://github.com/nodejs/tooling/issues/40)
  * still has experimental flag
  * original exception context is printed, landed via https://github.com/nodejs/node/pull/33491
  * Ian is supposed to push this to production and give feedback (performance, memory usage).  good luck Ian
* argument parsing [#19](https://github.com/nodejs/tooling/issues/19)
  * [implementation!!](https://gist.github.com/boneskull/872acd4c7afaa03260b48a9ecdca172c)
  * we need to meet Chris Ruy Ben
  * action Item: BEN make meeting
* Code Coverage Feedback:
    * https://twitter.com/mikeal/status/1271464985441361920


## Q&A, Other

## Upcoming Meetings

* **Node.js Foundation Calendar**: https://nodejs.org/calendar

Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.


