Kohei Ueno
Kohei Ueno
It is a great honor for me to be a Node.js Collaborator. Thanks for the nomination!
I'd like to work on - `packages/gatsby-cli/src/reporter/loggers/ink/components/messages.js` (edited) - `packages/gatsby-cli/src/reporter/constants.js`
I'd like to try - `packages/gatsby/src/utils/get-cache.js` - `packages/gatsby/src/utils/get-latest-apis.js` - `packages/gatsby/src/utils/get-public-path.js`
How about adding a new option like `opts.token` and set it directly to `this[kProxyHeaders]['proxy-authorization']`? ```js if (opts.token) { this[kProxyHeaders]['proxy-authorization'] = opts.token } ``` ```js // user land const agent =...
any update?
> Shouldn't this be solved from the consumer side that can call Debugger.resume (or some such) after attaching with --inspect-brk? Yes, the `--inspect-wait` flag acts like a combination of `--inspect-brk`...
cc @nodejs/inspector
@daeyeon Done
Do the CI failures have something to do with this change?
@jasnell @daeyeon I've updated the Node.js debugger documentation to clarify the difference between the three flags. Please review it again and let me know if you have any better ideas....