Correct the state of the `opencv4nodejs` package on the NPM.

justadudewhohacks / opencv4nodejs

Nodejs bindings to OpenCV 3 and OpenCV 4

MIT License

4.97k stars 827 forks source link

Correct the state of the `opencv4nodejs` package on the NPM. #860

Open issuefiler opened 2 years ago

issuefiler commented 2 years ago

You could either

deprecate the opencv4nodejs package on the NPM,
or better yet, change the GitHub repository URL, and invite @UrielCh as a maintainer or transfer the ownership of the package to him. (This way, we could keep using opencv4nodejs maintained by @UrielCh under the name of import OpenCV from "opencv4nodejs";.)

Another good option would be

issuefiler commented 2 years ago

Sorry, accidentally pressed the Comment button.

Another good option would be claiming the ownership of the opencv package. This can be done by contacting the NPM support with an agreement by @peterbraden.

@justadudewhohacks, @UrielCh.

issuefiler commented 2 years ago

@piercus.

UrielCh commented 2 years ago

Deprecate an npm package require npm access.

piercus commented 1 year ago

@issuefiler i cannot do anything here without the help of @justadudewhohacks

peterbraden commented 1 year ago

I'm not sure what this has to do with the opencv module which is separate.

Although it's not actively feature developed, a lot of people use the opencv module, and I wouldn't support changing the API to point at this module.