-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
[Critical Bug] Changes to JSONObject
in [email protected] are breaking jupyterlab extension builds
#83
Comments
JSONObject
in [email protected] are breaking jupyterlab extension buildsJSONObject
in [email protected] are breaking jupyterlab extension builds
pinging @blink1073 @GordonSmith |
Yeah we should revert that change and make a 1.5.2 |
In his commit message for the So it sounds like the revert will have to remove the entirety of 36debf6/the typescript 3.9 upgrade |
- fixes jupyterlab#83 This reverts commit 36debf6.
An attempt to fix jupyterlab#83 while keeping the bump to typescript 3.9.2
It would be nice if we could keep the typescript upgrade, so I've now also added a minimal PR (over at #85) that just reverts the changes to update
It does not. See details at #85 (comment). @GordonSmith Unless you have a quick and easy fix for this, I think our only reasonable option is to revert 36debf6 in full (by pulling in #84) and then do a release ASAP @blink1073 Do you agree? |
If I try to build the latest master of jupyter-fs:
I get the following error on the
tsc
(ie typescript compilation) step:This is definitely being caused by the latest release of
@lumino/coreutils
, since if I add a resolution to the previouscoreutils
to mypackage.json
:the build error is fixed.
I beleive the underlying cause is the redefintion of
JSONObject
that was part of the 1.5.1 release.@lumino/[email protected]:
lumino/packages/coreutils/src/json.ts
Lines 26 to 30 in 00ae441
@lumino/[email protected]:
lumino/packages/coreutils/src/json.ts
Lines 26 to 30 in 36debf6
Because this was a patch release of coretuils (1.5.0 => 1.5.1), you'll likely only see the bug if you delete your
yarn.lock
(or if start from a fresh build that never had one).The text was updated successfully, but these errors were encountered: