IPywidget error in Jlab 2.0

I have an ipywidgets extension that works on jlab 1.2.6 but getting some trouble on jlab 2.0 with jupyterlab-manager 2.0

I’m getting a:

Error: No provider for: jupyter.extensions.jupyterWidgetRegistry.

I’m getting some duplicates on my build which from what I understand might cause this.

WARNING in d3-array
  Multiple versions of d3-array found:
    1.2.4 ./~/d3-geo-projection/~/d3-array from ./~/d3-geo-projection/~/d3-array/src/index.js
    2.4.0 ./~/d3-array from ./~/d3-array/src/index.js

WARNING in entities
  Multiple versions of entities found:
    1.1.2 ./~/entities from ./~/htmlparser2/lib/Tokenizer.js
    2.0.0 ./~/dom-serializer/~/entities from ./~/dom-serializer/~/entities/lib/index.js
    
WARNING in semver
  Multiple versions of semver found:
    6.3.0 ./~/semver from ./~/@jupyter-widgets/jupyterlab-manager/lib/manager.js
    7.1.3 ./~/vega-embed/~/semver from ./~/vega-embed/~/semver/index.js

Is this an issue in jupyterlab manager or am I missing something else on my dependencies?

[jasongrout]

@consideRatio - you can go into the actual staging directory and figure out from there which extension is pulling in older versions. Do jupyter lab path to find your application directory, then go into that directory’s staging subdirectory. You can inspect the yarn.lock file to see what is being pulled in, and you can use yarn why to ask it to trace the dependencies.

[mattiaswangblad]

Ok so I got it to work now. I guess my idea to update the extension doesn’t really work.

I used to update with npm pack jupyter labextension install pyesasky-1.2.10.tgz without updating the version number between the dependency updates. Not entirely sure when in this process I first changed version number.

instead of jupyter labextension install .

which creates some random name on the package in the extensions folder. So I guess my updates got caught in some cache even though I ran jupyter lab clean --extensions

I’m a bit unsure which dependency removal fixed this. Still having the same build warnings so they were not the issue. Thanks a lot for all your help @jasongrout