-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Building Jupyterlab plugin from source does not pull working directory changes #1299
Comments
Not sure if the same thing. But I'm unable to install the jupyter labextension because I get a similar can't resolve fs error |
Are you installing the extension from NPM, i.e. |
Yeah I'm on jupyterlab 3.0.5 doing |
This was broken prior to the release of 0.6.0, but your install wouldn't work anyway as we didn't support jupyterlab 3 until after 0.6.0. |
Could you clarify for me. Shouldn't 0.6.0 work for jupyterlab 3? If so, those are the versions I'm trying to install. Are these not the same issue? |
The next version we dist will be compatible for Jupyterlab 3 - 0.6.0 remains compatible with Jupyterlab 1 and 2 only. The issue I'm working on refers to changes from local working directories not picked up during the development build process, which does not affect whether the plugin will build on Jlab 3 once the new compatible version is disted. Sorry if there was any confusion! |
Previously, when I built the
perspective-jupyterlab
plugin, it would pull in changes from other packages in Perspective—thus I could make a change inperspective-viewer
and see it reflected in Jupyterlab, etc.Since #1231, building the Jupyterlab plugin no longer pulls in changes from the local working directory, an issue which I fixed here as part of #1289, before the Jlab 3 PR (#1294) was merged. The issue with it not resolving working directory changes was due to
externals: [/^[a-z0-9@]/],
which meant thatperspective
was not being bundled into the Jupyterlab plugin, and so the plugin could only pull the disted version of Perspective (assuming my understanding of Webpack in this case is correct).I tried to implement the same fix on top of #1294, but
jupyter lab build
fails with this error:I have added
node: {fs: "empty"}
toplugin.config.js
and the same issue happens, and we are definitely not importing 'fs' anywhere in our disted assets - @timkpaine not sure if you have insight into this issue/have a good direction to look.The text was updated successfully, but these errors were encountered: