James Messinger

Results 225 comments of James Messinger

Also... a little back-story: I'm actually the one who [added browser support](https://github.com/chaijs/chai-http/pull/70) to Chai-HTTP. It was pretty easy, actually. I just used Browserify, and made a few tweaks to the...

:+1: Cool, glad to help. Here's a [subsequent PR](https://github.com/chaijs/chai-http/pull/73) that improved the browser build for Chai-HTTP

The "leave as is" option was added because some people wanted Version Bump Prompt to do all the other stuff that it normally does (update other files, git commit, tag,...

If I understand your needs correctly, I believe you can already do that. There are a couple ways... Option 1 - Replace old version with new version -------------------------------------------------------- You can...

I love this idea! Would gladly accept a PR to add this functionality. You could use a library like [rc](https://www.npmjs.com/package/rc) or [cosmiconfig](https://www.npmjs.com/package/cosmiconfig) for this.

Very good point. I think the typical thing that most CLIs do is allow boolean arguments to be prefixed with `no-`. So you could do `bump --no-commit --no-tag`

This may be a limitation of Husky. Perhaps it doesn't support tools that prompt for user input. Or perhaps there's something you need to configure in Husky to make it...

I created a new npm package named [**coverage-istanbul-loader**](https://www.npmjs.com/package/coverage-istanbul-loader). It includes [the fix mentioned above](https://github.com/webpack-contrib/istanbul-instrumenter-loader/issues/73#issuecomment-427665948) as well as other fixes and updated dependencies.

I created a new npm package named [**coverage-istanbul-loader**](https://www.npmjs.com/package/coverage-istanbul-loader). It includes [the fix mentioned above](https://github.com/webpack-contrib/istanbul-instrumenter-loader/issues/73#issuecomment-427665948) as well as other fixes and updated dependencies.

@big-r81 - Thanks for opening this issue. Yes, the redirects should be handled in `http.js`. Is this only happening in Node, or also in web browsers? I'm pretty sure that...