getImageUrl sub-domain mismatch about node-hitomi

[H2Owater425]

I found what's wrong with them, Hitomi used to use the number of frontends to get the first letter of the subdomain, but recently they changed that into a meaningless number.
I tested the new code and worked well, as I said in #11, a new feature premeditated in #8 will be added with the bug fix in future release.

[H2Owater425]

I guess Hitomi recently changed its method to get the subdomain of the image again. I'll examine Hitomi's code as soon as I get arrived at home.

[H2Owater425]

I released a new release with few bug fixes including this one, please check it out!
Release [email protected] · H2Owater425/node-hitomi

[H2Owater425]

Okay, I just checked that hitomi rewrote it's subdomain-creating logic.
I think I have to examine again to write the code, since it is too late in my time zone, I'll do it later, sorry...

[dnm13]

Okay, I just checked that hitomi rewrote it's subdomain-creating logic.
I think I have to examine again to write the code, since it is too late in my time zone, I'll do it later, sorry...

don't worry about rushing it
and you've done nothing to apologize for

[H2Owater425]

Even there's been a lot of big ups and downs, the new version of the package has finally been released!
Thanks for noticing me about the errors to let me fix them, here's the changelog (and what I have done wrong 😥) about this update Release [email protected] · H2Owater425/node-hitomi!

[dnm13]

great job!
it works properly now, thanks for fixing it :)

[dnm13]

it occasionally would return invalid / wrong sub domain

from browser inspect:

you can check it from code 1989850 page 47 (the picture said 46 but it's because index start from 0)
going to reopen the issue with this comment. hopefully you can fix it

[dnm13]

works like charm
thanks for the quick fix! much appreciated :)