Darshan Sen
Darshan Sen
@betochf Could you please rebase and resolve the merge conflicts?
Gentle ping @zbjornson, in case you missed ^
@SimenB good idea, done!
**WORKFLOW DISABLED TEMPORARILY**
It seems to be a problem with `npm v6.14.4`. Does this help: https://github.com/npm/cli/issues/1185?
How about this: ```js require('fs').writeFile( 'some_non_existent_directory/test.txt', '', err => console.trace() ); ``` It produces: ```sh ❯ node index.js Trace at .js:4:18 at node:fs:1472:7 at FSReqCallback.oncomplete (node:fs:179:23) ```
How about this? #### test.js ```js const { spawn } = require('child_process'); const installProcess = spawn('npm', ['install', 'lodash'], { stdio: 'inherit' }); installProcess.on('close', (code) => console.log(`exit code: ${ code }`));...
We can write a wrapper around `spawn` to accept a callback. Here is a very basic implementation of what I mean: ```js const util = require('util'); const { spawn }...
Could you please share the code? The child process does seem to be able to connect to the internet here: ```js // test.js require('child_process'). exec('node child.js'). stdout.pipe(process.stdout); ``` ```js //...
The quickest and the most affordable way for funding the development of specific things is for you to get in touch with the individual maintainers and sponsor them directly instead...