Building bleeding edge jupyterlab

[Christian Schafmeister]

Hi,

What is the best practice for building bleeding edge jupyterlab with extensions?

We are building a bleeding edge jupyterlab application that contains two extensions (nglview and bqplot).  

We have wholesale translated the Python code for these widgets into Common Lisp and we need to guarantee that the Javascript code for these extensions precisely matches the Common Lisp code and the Python code.

So we are installing the jupyter extensions from local source directories using the code below.

jupyterlab comes up immediately and then it appears to build the jupyterlab application again and again every time I hit the "Reload" button on my browser reloading jupyterlab.

Why is this?  

Is there any way to build the jupyterlab Javascript application once and for all - before I start jupyterlab?

/opt/clasp/bin/jupyter-labextension install @jupyter-widgets/jupyterla...@0.37 --no-build

# Don't rely on npm/yarn/whatever to install nglview widgets

/opt/clasp/bin/jupyter-labextension install /opt/clasp/lib/quicklisp/local-projects/cl-nglview/js --no-build

# Don't rely on npm/yarn/whatever to install bqplot widgets

/opt/clasp/bin/jupyter-labextension install /opt/clasp/lib/quicklisp/local-projects/cl-bqplot/js --no-build

/opt/clasp/bin/jupyter-lab build

Christian Schafmeister,

Professor, Chemistry Department

Temple University

[Steven Silvester]

Hi Christian,

Currently, installing from a local directory is in effect a link.  We run `npm pack` to determine whether the extension has changed on disk.  It shouldn't prompt you to rebuild unless it computes a different SHA sum, is it giving you false positives?

Regards,

Steve

On Friday, August 24, 2018 at 2:30:36 PM UTC-5, Christian Schafmeister wrote:

Hi,

What is the best practice for building bleeding edge jupyterlab with extensions?

We are building a bleeding edge jupyterlab application that contains two extensions (nglview and bqplot).  

We have wholesale translated the Python code for these widgets into Common Lisp and we need to guarantee that the Javascript code for these extensions precisely matches the Common Lisp code and the Python code.

So we are installing the jupyter extensions from local source directories using the code below.

jupyterlab comes up immediately and then it appears to build the jupyterlab application again and again every time I hit the "Reload" button on my browser reloading jupyterlab.

Why is this?  

Is there any way to build the jupyterlab Javascript application once and for all - before I start jupyterlab?

/opt/clasp/bin/jupyter-labextension install @jupyter-widgets/jupyterlab-man...@0.37 --no-build

# Don't rely on npm/yarn/whatever to install nglview widgets

/opt/clasp/bin/jupyter-labextension install /opt/clasp/lib/quicklisp/local-projects/cl-nglview/js --no-build

# Don't rely on npm/yarn/whatever to install bqplot widgets

/opt/clasp/bin/jupyter-labextension install /opt/clasp/lib/quicklisp/local-projects/cl-bqplot/js --no-build

/opt/clasp/bin/jupyter-lab build

[Christian Schafmeister]

Hello Steve,

It is building very often and very reproducibly.

Could you elaborate on "installing from a local directory is in effect a link"? 

I'll take a closer look at SHA sums and play with 'npm pack' to see if it gives me any indication that it wants to rebuild things.

Are there any other tests I can run that would provide useful feedback?

Best,

.Chris.

[Steven Silvester]

We treat an install of a local directory as "live" in that its contents might change at any time. It is not a true link in the "npm link" sense because "npm link" prevents deduping of dependencies, something that is required for JupyterLab's dependency injection system. As for the tar sum, here is the function we are using in jlab to compute it, since the hash of the tarball itself is unstable: https://github.com/jupyterlab/jupyterlab/blob/3201e4714ae85f3c21f0218261826595d55af518/jupyterlab/commands.py#L1550

Regards,

Steve

[Christian Schafmeister]

Oh - ok - that makes sense that local directories should be considered "live".

How does it work though?  The jupyterlab application comes up instantly when I connect the browser - and then it builds jupyterlab and loads it again?

[Steven Silvester]

When you launch JupyterLab it shows you the previously built application.  Then, it runs checks in the background to see if it needs to be rebuilt, prompting you to do so if it detects changes.

Regards,

Steve

On Friday, August 24, 2018 at 2:30:36 PM UTC-5, Christian Schafmeister wrote:

Hi,

What is the best practice for building bleeding edge jupyterlab with extensions?

We are building a bleeding edge jupyterlab application that contains two extensions (nglview and bqplot).  

We have wholesale translated the Python code for these widgets into Common Lisp and we need to guarantee that the Javascript code for these extensions precisely matches the Common Lisp code and the Python code.

So we are installing the jupyter extensions from local source directories using the code below.

jupyterlab comes up immediately and then it appears to build the jupyterlab application again and again every time I hit the "Reload" button on my browser reloading jupyterlab.

Why is this?  

Is there any way to build the jupyterlab Javascript application once and for all - before I start jupyterlab?

/opt/clasp/bin/jupyter-labextension install @jupyter-widgets/jupyterlab-man...@0.37 --no-build

# Don't rely on npm/yarn/whatever to install nglview widgets

/opt/clasp/bin/jupyter-labextension install /opt/clasp/lib/quicklisp/local-projects/cl-nglview/js --no-build

# Don't rely on npm/yarn/whatever to install bqplot widgets

/opt/clasp/bin/jupyter-labextension install /opt/clasp/lib/quicklisp/local-projects/cl-bqplot/js --no-build

/opt/clasp/bin/jupyter-lab build