update npm package repo about jupyterlab-execute-time

[mlucool]

The npm version is no longer supported. Please upgrade to lab@3 or lab@4 and use the python installation method - https://github.com/deshaw/jupyterlab-execute-time?tab=readme-ov-file#install

[lneves12]

My use case is slightly different. I have an application that uses jupyter lab underneath as a different entry point. Basically it runs in a decoupled way from the server. It's built in a similar way to https://github.com/datalayer/jupyter-ui , where I control the new JupyterLab().start() code.

In this case I can't install this extension using python, only npm

[lneves12]

let me know if this doesn't make sense for you to maintain, and I can also keep my own package, I just thought this could be useful for other folks, but it might be that my use case is just very uncommon.

Thank you!

[krassowski]

In this case I can't install this extension using python, only npm

You can fetch the tarball from PyPI and place the place the prebuilt extension in a place from all other prebuilt (module federation) extensions get loaded see https://jupyterlab.readthedocs.io/en/stable/extension/extension_dev.html#prebuilt-extensions - this is assuming your custom implementation does support prebuilt extensions (which would be a pretty reasonable ask). I suspect with time more and more extensions will move away from publishing on NPM especially if they are not extensible themselves.

[lneves12]

I don’t really have module federation and support dynamically installing pre built extensions. I am bundling the jupyter lab myself (module federation doesn’t make sense to my use case).

The ideia is that I can easily serve my custom jupyter lab from a CDN. We also have our custom implementation of the contents API, so we can even load the lab UI before having a kernel container ready.

Anyway, I guess I can also fetch the tarball, as you suggested, and import the extension static files from there.

Thanks for the replies 👍