My custom Jupyter Notebook extension consist of the main.js file but also other files - JS helpers and React build artifacts. I install the package and enable the extension using the command
When I run the extension in the Notebook however, only the main.js file is exposed on the server. Fetching others results in 404 error making the extension unusable.
Expected behaviour
All files are exposed on the server as it's in the case of the "desktop version" of Jupyter Notebook
Actual behaviour
Only the main.js file is exposed on the server making the extension unusable.
Thank you @drzamich for a beautifully written issue! I think this is a symptom of something that has been observed in other context as well, but I'm not sure what is going on.
Bug description
My custom Jupyter Notebook extension consist of the
main.js
file but also other files - JS helpers and React build artifacts. I install the package and enable the extension using the commandAll of the files are properly copied to the
nbextensions
directory:When I run the extension in the Notebook however, only the
main.js
file is exposed on the server. Fetching others results in 404 error making the extension unusable.Expected behaviour
All files are exposed on the server as it's in the case of the "desktop version" of Jupyter Notebook
Actual behaviour
Only the
main.js
file is exposed on the server making the extension unusable.How to reproduce
nbextensions/mstr_jupyter
directorymain.js
file is there.Your personal set up