-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
bug: menu fails to render #7726
Comments
Also experiencing the same issue. |
@vince-fugnitto do you currently have a workaround available? |
Based on the PR, you can try to force the desired version of "resolutions": {
"**/**/moment": "2.24.0"
}, |
It does work for me. We'll have to use this as a workaround until the maintainers fix the (First time installing theia; I thought the broken UI was really the awesome ide everyone's happy about lamo) |
It work for me too, ths |
Due to eclipse-theia/theia#7726, maybe something to do with momentjs
Due to eclipse-theia/theia#7726, maybe something to do with momentjs
There are 2 things:
|
I don’t think it was a missing command, as it is just a broken dependency. |
Fix for eclipse-theia/theia#7726 Signed-off-by: Akos Kitta <kittaakos@typefox.io>
@vince-fugnitto it is fine to pin it. But I meant that the menu registration should not blow up the whole menu bar if one command failed to be registered. |
Yes I agree, there should be better handling in order to prevent such issues, especially since it breaks the entire main menu. |
Should we open a follow-up issue to be more robust when creating menus/commands and not fail if one is missing? |
Fix for eclipse-theia/theia#7726 Signed-off-by: Akos Kitta <kittaakos@typefox.io>
@vince-fugnitto yes, thanks |
|
Bug Description:
The application's main-menu fails to render due to an error with momentjs:
The following error has been reported and reproduced in a number of ways:
There is an issue where others have expressed similar breaking changes for moment and they performed the same rollback in version:
Steps to Reproduce:
There are numerous ways to produce the bug, one possible way is to run the docker image, or to compose your own application following the guide from the website.
The text was updated successfully, but these errors were encountered: