Through the heavy usage of the extension template project, almost all updated extensions out there depends on the build dependency: hatch-nodejs-version. As it is currently affiliated to Angus (thanks a lot for that great plugin), it would be better for the long term maintenance to host that project under a community organization.
Proposed Solution
As jupyterlab GitHub org is already hosting the other essential hatch plugin for packaging JS assets in a Python package - aka hatch-jupyter-builder - and after quickly exchanging about this with @agoose77. I propose to transfer hatch-nodejs-version to the JupyterLab organization and related to it the pypi package.
Problem
Through the heavy usage of the extension template project, almost all updated extensions out there depends on the build dependency: hatch-nodejs-version. As it is currently affiliated to Angus (thanks a lot for that great plugin), it would be better for the long term maintenance to host that project under a community organization.
Proposed Solution
As jupyterlab GitHub org is already hosting the other essential hatch plugin for packaging JS assets in a Python package - aka hatch-jupyter-builder - and after quickly exchanging about this with @agoose77. I propose to transfer hatch-nodejs-version to the JupyterLab organization and related to it the pypi package.