Closed jenshnielsen closed 2 years ago
Hi @jenshnielsen, thanks for the PR!
So, actually, one thing worries me about the PR, setting everything for the latest version could cause some version conflicts in user's machines that depend on older software. I asked my colleagues and the preferred way to go about versioning is by adding a lower boundary of suport and a high one. For the low, I'd say we can use whatever it was the lowest before and for the highest, we can use the new values you added on this PR. What do you think?
example:
node>=13.2.0,<=17.0.0
Hey @jenshnielsen thanks for opening this, but I updated it with npm update
seems like the recommend way of doing by npm and seems to work fine.
I have manually tested that this works correctly for me in both Jupyter lab 3 and notebook.
With this change all javascript dependencies are up to date except the following which requires an apation of the tooltip calls since tippy/popper has changed their api.