👈 Launch a Binder on branchbrichet/notebook/ui-toolkit_shared_scope

Since the corresponding PR in jupyterlab has been published in 4.1, we should probably backport this one to7.2.x and7.1.x branches.

I guess it would be fine to backport to7.2.x since7.3.0 was released today. Not sure it's worth it for7.1.0 though, unless someone actively requests it, and since it probably affects just a few extensions?

@meeseeksdev please backport to 7.2.x

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 7.2.xgit pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 21d0306ecef93ea23bf063bc1d8a0580450cd4df

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #7530: Adds jupyter-ui-toolkit packages in shared scope'

4. Push to a named branch:

git push YOURFORK 7.2.x:auto-backport-of-pr-7530-on-7.2.x

5. Create a PR against branch 7.2.x, I would have named this PR:

"Backport PR#7530 on branch 7.2.x (Adds jupyter-ui-toolkit packages in shared scope)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove theStill Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free tosuggest an improvement.

I can do it

ah meeseek was not able to do the backport, hopefully the manual backport is not too painful since it's just a few lines.