Bob Thomas

It looks like this is a problem with the inquirer library that commitizen uses for prompting: https://github.com/SBoudrias/Inquirer.js/issues/793

I ran into the same issue, but with the description text for a custom filter. This breaks standard OpenAPI tools (I would assume any YAML parser that is not Python...

I opened a discussion, which the new issue template requests, but there were no replies. I'm trying to be respectful of the maintainers here, but I'm not sure what to...

This has already been fixed in #2697

According to #2872, sometime this week or next.

Adding webpack-resolver to my create-react-app project leads to a huge increase in compile time, and adds hundreds of files to the build directory - I assume one for each module...

I don't really have control over node's decisions here, I just need to live with them. I realize I can catch these errors at the process level, but I would...

> > by potentially killing it, unless worked around in some way > > Killing the process was always possible with memory consumption `FATAL ERROR: Reached heap limit Allocation failed...

It seems like this is fixed in 0.15.0, but https://jmespath.org/ is using 0.14.0. This just needs to be fixed in https://github.com/jmespath/jmespath.site

The CI build did run on the greenkeeper branch, but failed the styleguide build: ``` #!/bin/bash -eo pipefail yarn styleguide:build yarn run v1.13.0 $ run-p build write-styleguide-sections $ node scripts/build...