Moxley Stratton

 Open the Developer Tools panel, then run the test again. What is the `ruby-test` debug output shown in the panel? Also, do you have a debug session running?

@butsjoh: What command is ruby-test running for your tests?

Also, what tool are you using to colorize the output?

On working on #67, I noticed that the two dash arguments passed to the shell program were in the wrong order: `zsh -c -l {command}`. It is now corrected to...

With the latest update, which unbuffers the output, I can at least see the debug prompt (using binding.pry). The next step is to accept user input for the debugger.

For pry-byebug at least, you can prefix the test command with `echo continue |`.  With some research, there is likely to be a way bypass most debuggers.

Here's how I imagine it working: 1. Process the output by splitting it into parts that are file paths, and parts that are everything else. 2. For the everything-else parts,...

> Note npm install generated a new package-lock.json with "lockfileVersion": 2 and updates to the dependency tree. I think the new package-lock.json should be included with the PR. @kenkunz: I've...

The challenge is that it is difficult to differentiate between an Ecto type and an Ecto schema. Using your example, right now, params supports something like this: ```elixir use Params.Schema,...

Part of the problem is that the `deps/argon2_elixir/priv` directory exists as part of the `argon2_elixir` package. In the `elixir_make` API docs, it says: > The "priv" directory must not exist...