-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fails for Mocha #3
Comments
so sorry for the late reply, I was out with a bad cold for a couple of weeks. I'll address this ASAP. thanks for the issue edit: btw, thanks for the suggestions as well. We'll make those changes. It's awesome that you're looking to use this with mocha, I'm sorry I wasn't able to get this taken care of faster. |
no rush; I'm well-acquainted with providing free support and bug fixes for software 😄 |
@boneskull I updated The error should be gone if you reinstall and run I'll leave this open to address the other suggestions. We'll probably create individual issues around those and then we can close this issue. |
Wanted to get this into our publishing workflow, but ran into varied difficulties.
First problem is that there's something weird going on in either
repo-utils
,expand-pkg
, orparse-git-config
. Was trying to fix this, but onceparse-git-config
giving me problems, I crawled back out of the rabbit hole.To reproduce badness:
npm install -g update update-contributors
update init
, choosecontributors
update
in mocha working copyMocha's
package.json
has a stringhomepage
value and an objectrepository
value.I tracked the problem to the weirdness happening in
lib/expanders/git.js
ofexpand-pkg
:I'm not sure why we're looking at
config.repository
and then expandingconfig.homepage
. The intent of this function is unclear. To convince myself I was sane, I created a failing test:Anyhow, there were a bunch of other failing tests here, because of problems in
parse-git-config
and its ilk. Here are some:FWIW, this is my .gitconfig. If the format is invalid, Git is not complaining about it.
This is where I gave up and decided to tell you about it. 😄
Anyway, once I disabled the weirdness caused by
expand-pkg
'slib/expanders/git.js
, I got some contributors:You can see the current values here.
The text was updated successfully, but these errors were encountered: