Please update NPM

[AndrewAdamson]

Its mentioned in previous issues that you do not use NPM but please find a way to update

Or at least update readme to notify NPM is not maintained/out of date.

[photopea]

There is no mention of any NPM in README. If you want, you can put it on NPM, but the only version, which I am maintaining, is the one here on GitHub.

[jardicc]

@photopea The thing is that it has about 1 000 000 downloads by developers every week. So it is used a lot as depencency by other modules. But everything you fixed in this github repo in last 3 years is still broken there and improvements not applied. https://www.npmjs.com/package/utif ...and I don't know who has access to update it.

[photopea]

@jardicc could you put the latest UTIF.js onto NPM? I would put UTIF.js on NPM myself, if it could be done through a web browser. I do not want to install some 200MB command line python socket script nonsense, just to upload a 64 kB file to their server.

[jardicc]

I don't think I have access to do that. I wrote e-mail to that person. Otherwise we would need to create separated module and let other devs to know that they can switch to updated code.

[jardicc]

@beetes-juice In the end I made a copy here: https://www.npmjs.com/package/utif2

[Steve-Mcl]

@photopea

I would put UTIF.js on NPM myself, if it could be done through a web browser. I do not want to install some 200MB command line python socket script nonsense, just to upload a 64 kB file to their server

Does npm publish depend on python?

I am sure I have previously executed npm publish (installed with nodejs) on a system without python even being installed?

@jardicc @photopea I'm sure you already know but for completeness, you can get scimonsters contact info by running npm info utif - I'm certain if they are still around they would update the package or permit @photopea publish rights? (PS, @Scimonster is also on github - maybe another way of contacting them?)

[photopea]

Could you ask NPM to delete the current version? And then, you can upload a new version?

[Steve-Mcl]

Could you ask NPM to delete the current version? And then, you can upload a new version?

@photopea

That is not how NPM works. There are currently over 1000000 downloads of your package per week...

Very impressive. However, NPM will not delete this nor will they delete any older versions as other packages still depend on them.

The best way to maintain integrity is for you to gain access (publish rights) to this package (which only @Scimonster can grant) or for @Scimonster to publish an updated version.

IMPORTANT NOTE: I notice your package has been updated but the version number inside package.json has not change. This really should be updated with each modification following sematic versioning rules. Also note, until you actually bump the version from 3.1.0 to a new version number, @Scimonster couldnt publish your latest changes anyhow (NPM requires the version number inside package.json to be changed with each publish - thats how package dependancies know something has changed (major.minor.patch sematic version change)

[jardicc]

@jardicc @photopea I'm sure you already know but for completeness, you can get scimonsters contact info by running npm info utif - I'm certain if they are still around they would update the package or permit @photopea publish rights? (PS, @Scimonster is also on github - maybe another way of contacting them?)

I contacted him via e-mail and got no reply. Therefore I created Utif2

[jardicc]

After a year I updated UTIF2 again: https://www.npmjs.com/package/utif2 to version 4.1.0

[photopea]

Thanks a lot! :)

[varun-raghavendra]

Which is the new UTIF repository after the update? The same one as this?

[hipstersmoothie]

@jardicc could you update it again? It's been another year and it looks like some bug fixes have shipped

[jardicc]

@hipstersmoothie I think I will once I find a time. One of the change seems to be embedding pako into src file itself. So removing dependency. But otherwise I have no clue what changed... there is no changelog, no commit messages, no versioning.

And I think this thing can break it for NodeJS 11ce21f#diff-aa0d4be33d6a5f7da30b7b6e46a90849c7db6a1c262821061b4811e6bb0d7b00L1415

So I have no other option than increment major version to not break it for others.

[hipstersmoothie]

Seems like a good move