Why is the current NPM release `1.0.0` different?

[nicholaschiang]

There are significant differences between the v1.0.0 tag and the master branch. Why? Why haven't you released a new version to NPM? The newest version there (v1.0.0) is over two years old...

[nicholaschiang]

@sidorares there seems to have been significant changes and bug fixes since that v1.0.0 tag. Could you push those to NPM?

[sidorares]

yes I probably should. Due to a significant time gap between releases major version bump might be a good idea ( not that I'm aware of any backwards incompatibilities, just as a precaution )

[nicholaschiang]

Would you need help with this? I'd be more than happy to contribute!

[sidorares]

Would you need help with this? I'd be more than happy to contribute!

thanks for the offer! I'm slowly migrating all the projects to gh actions - if you have time to help with that would be great

[tomercohen1210]

@sidorares do you think the new version will come out soon?

[ldt1997]

I meet problems with float numbers and would like to use the new version

[justinpark]

@sidorares any updates for the release? I also encounter the same problems with float numbers and would like to use the new version

[ThallesP]

Hi @sidorares could you at least publish the latest version on NPM? Even doing manually would be good with npm publish.

Currently I've to do an NPM install from this Github repository, locked at a specific commit, which isn't that good.

[sidorares]

@ThallesP I promise I'll give this library some attention over a coming weekend.

[aladdin-add]

@sidorares friendly ping! :)

[riflowth]

@sidorares Friendly reminder. I face some problem in my production code (related to https://github.com/sidorares/json-bigint/issues/49)