Use nodejs version plugin

[blink1073]

cc @fcollonval @agoose77 @ofek

[blink1073]

@fcollonval this approach won't work unless we backport the changes to federated_labextensions.py to look for the package name in pyproject.toml first.

[ofek]

lgtm. here's another example from earlier today https://github.com/squidfunk/mkdocs-material/blob/9603c71adafe5959e57584a4982ee03d340a7be3/pyproject.toml

[agoose77]

@blink1073 I'm not sure I'm following. Do you mean for older JupyterLab versions that won't have the latest federated_labextensions.py?

[agoose77]

I realised that the docs weren't clear for the metadata hook, so I've updated them. The fields setting corresponds to the names in the pyproject.toml file that are provided by the extension. This is so that other metadata plugins can be used alongside this extension (as hatch-nodejs-version does more than one thing).

[blink1073]

Do you mean for older JupyterLab versions that won't have the latest federated_labextensions.py?

Yes, the changes are in 4.0alpha but have not been backported to 3.x yet.

[blink1073]

jupyterlab/jupyterlab#13076