Closed Kanaye closed 4 years ago
Would also like to know
If you look at the diff for v1.6.0 the only file changed was the package-lock and the only change there was the version number. That is probably why it was not released to NPM.
If that would be true, that would leave the question open: Why make a release without changes, but it isn't. I guess you only viewed that changes the release commit for 1.6.0 made. But you need to look at all 11 commits between release 1.5.0 and 1.6.0. And that changed a lot more than just a version number: https://github.com/tmijs/tmi.js/compare/v1.5.0...v1.6.0
I didn't publish to npm because there were more changes I needed to make and more event support to add. I haven't put in the effort to do that with the countless other projects I'm working on. I'm not entirely sure how to proceed on tmi.js@1.x
at the moment. A 1.6.x
publish will come sooner than later. (I'll probably be skipping the 1.6.0 publish)
Okay that's fair. Thanks for your answer and your work on tmi.js
Hi! Just noticed that there is a 1.6.0 Release on Github. Will this release be published on npm or is there some reason it hasn't been released over there ?
Thanks.