JD

For me, the problem was that I had some warnings when I built the project in a CI environment (when `CI=true`). When CI is set, react-scripts build will treat warnings...

> Me too. Could you please @PGuimarais tell me how to deploy manually b/c I'm new on this Just run the `deploy` command from terminal.

I think the question is: When I have multiple stages (dev, prod) how do I define different values to my environment variables (e.g. REACT_APP_API_URL) for each stage, using the same...

Bump. I'm still getting this. Anyone have any pointers?

Hmmm.. Yes I see the conundrum. How do you currently debug the code? Could the invocation be changed to allow passing `--inspect` (or `--inspect-brk`) as an `arg` by the caller...

Something like this _may_ work (changes to [run-in-node.js](https://github.com/architect/sandbox/blob/master/src/invoke-lambda/run-in-node.js)): ``` const fp = require("find-free-port") // find a free port - may be a better way than using this dep ... const...

Why would we need to terminate the process? Once it’s run doesn’t the process auto terminate? Having a debugger attached doesn’t change that - the code will execute and then...

Quick screen recording of this concept working on a simple eval'd code: https://youtu.be/tc6lgwbCxc4 Running the following code in terminal (load the content of a file into a variable, echo the...

> the process is held open as long as debugging continues With VS Code, once the code in the process has finished running, it sends a terminate signal to the...

Examples: [How to debug Node.JS child forked process?](https://stackoverflow.com/a/16843277/200653) [Debugging Node without restarting processes](https://hackernoon.com/debugging-node-without-restarting-processes-bd5d5c98f200) And an npm convenience package that does this (not suggesting introducing this as a dep): [child-process-debug](https://www.npmjs.com/package/child-process-debug)