Correct the state of the opencv4nodejs package on the NPM.

[issuefiler]

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]

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]

@piercus.

[UrielCh]

Deprecate an npm package require npm access.

[piercus]

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

[peterbraden]

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.