-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix compilation #28
Fix compilation #28
Conversation
We no longer ship the Jupyterlab code together with the python module, as it gets directly - and automatically - installed in the final destination.
@diocas should we have a look at the failed JavaScript check? |
Makes checks pass
maybe 3.0.2 or 3.1.0 release ? our usage failed with 3.0.1: we use this command to install |
@camper42 we removed version 3.0.1 because of that. This PR should fix the issue. We will tag a new version this Wednesday. |
never mind, thank you very much for your work in support of Lab 4 |
Aligned the compilation code with upstream (had to finally try to make it work), and now it builds the frontend components as well (these were being skipped).
Changed the name of the folder of the nbextension from "static" to "nbextension" (the Lab extension was inside "labextension", so it makes more sense this way).
Since the extension gets automatically copied to the final destination (and now the build code doesn't include the lab extension together with the Python module by default), I removed the possibility of manually installing it. This part of the code was (and would continue to) crash, since it was relying on the
package.json
file to retrieve the name (which was not necessary, but that's how it was).I believe none of this is necessary, but we can easily add it back.
Needs testing.