Edward Wang

Tried [`why-is-node-running`](https://www.npmjs.com/package/why-is-node-running): ```javascript "use strict" import { createRequire } from 'module' const require = createRequire(import.meta.url) const whyRunningJS = require('why-is-node-running') export const whyRunningLog = function() { whyRunningJS() } ``` and ```purescript...

> @edwardw I suspect it's the Node instance in the middle that it's hanging ([this one](https://github.com/purescript/spago/blob/726a45ba3784bce6b6b5e61d1e52a74994555fdd/src/Spago/Command/Run.purs#L121) that we launch to run the script), while the child node always terminates properly...

What I found out yesterday is that as soon as one puts node process in a pipe, its `stdin` changes from `Readable` stream to a `Socket`: just compare `node -p...

A workaround: ```purescript close interface + Stream.destroy Process.stdin ``` A previous comment mentioned that there is a missing `TickObject` if spago run directly. That object ultimately leads to [streams/writable.js#L760](https://github.com/nodejs/node/blob/v18.18.0/lib/internal/streams/writable.js#L760), which...

The "fix" is most unusual. I was trying to attack this again by adding this new test to `node-execa` package: ```purescript diff --git a/test/Test/Node/Library/Execa.purs b/test/Test/Node/Library/Execa.purs index e508ff1..72d369c 100644 --- a/test/Test/Node/Library/Execa.purs...

> > It is very ugly hack, should we add it to the readline package? > > Probably not. We've already identified a non-hacky fix; why consider this hacky idea?...

Another common scenario would be to insert an entry if absent and return an immutable reference to the value. Currently `OccupiedEntry::into_mut` and `VacantEntry::insert` all return a mutable reference, and what...