Hacker News new | ask | show | jobs
by Keithamus 1649 days ago
Hi, I'm the current lead maintainer of Chai.

We don't own the domain name, the previous maintainer/author does. It seems to have lapsed. There's not much I can do about that other than attempt to contact the previous maintainer, which I've done.

4 comments

I am not sure if you know, but domain registrars have a policy that allows the organization or company to be able to get ahold of the domain.

For example, if the domain is registered under a former employee and you cannot get ahold of that employee, the organization or company can fill out a form provided by the registrar to gain access to the domain.

This would certainly apply to you, and you should be able to get ahold of the domain name (and renew it). You will need to provide certain documents in order to prove that your organization should have access to the domain. What is required depends on the registrar.

Also, I would contact the domain registrar and tell them that you'd like to pay for the renewal (so they will change the name servers back to your previous name servers) while the details are worked out about domain ownership.

If you have any trouble with ANY of this, get in touch and I will help you get it taken care of, you should be able to find me via a search for my user id.

The subdomain chai.js.org is available and it may be worth investigating that as an alternative. (https://js.org/ has more details)
Much love. I like chai a lot. Thanks for your work.
Since you're here, and the online docs are currently missing, do you know the best way to a stacktrace from a failed Chai assertion? Basically, if I do:

    import chai from 'chai';
    chai.config.includeStack = true;
    try {
      chai.expect(1).to.equals(2);
    } catch (e) {
      console.log(e.stack);
    }
In the REPL, I'm getting `e` as an AssertionError with a trace, but in my running code, the error is coming back as a vanilla object without a stacktrace. Sorry that this is clearly not the right forum for this kind of question.
Failed expectations always throw an AssertionError, and they always have a stack. It might be the test runner you have which is breaking or hiding the stack?
Thanks; figured it out. I was passing the object to a parent thread and the class properties were being removed in the process. Thanks for the help.