Installation will not work if assets are not found and jupyter-packaging is not installed

[martinRenou]

If JavaScript build assets are not there and if jupyter-packaging is not installed, the installation will be broken without any error message. This is due to the following try-except:

https://github.com/jupyterlab/extension-cookiecutter-ts/blob/3.0/%7B%7Bcookiecutter.python_name%7D%7D/setup.py#L72-L84

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[krassowski]

Just came here to note the same after seeing https://discourse.jupyter.org/t/extension-migration-issue-from-jupyterlab-2-x-to-3-x/9871. The current implementation requires jupyter_packaging to be a runtime dependency, which should not be the case I think?

[meeseeksmachine]

This issue has been mentioned on Jupyter Community Forum. There might be relevant details there:

https://discourse.jupyter.org/t/extension-migration-issue-from-jupyterlab-2-x-to-3-x/9871/2