-
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
Theia does not run with Node.js v10.3.0
#2009
Comments
I can confirm this on Windows. The problem is the nsfw module. To fix the build I ran:
|
… be done from cmd.exe (don't need different shells) Closes eclipse-theia#1614 See also eclipse-theia#2009
… be done from cmd.exe (don't need different shells) Closes eclipse-theia#1614 See also eclipse-theia#2009
… be done from cmd.exe (don't need different shells) Closes eclipse-theia#1614 See also eclipse-theia#2009
… be done from cmd.exe (don't need different shells) Closes eclipse-theia#1614 See also eclipse-theia#2009
This seems to be fixed in version
I will verify it within Theia. |
No, it is failing because of Details:
|
It seems the Does it ring the bell, @AlexTugarev? |
This should not get to `master` for GH-2009.
… be done from cmd.exe (don't need different shells) Closes eclipse-theia#1614 See also eclipse-theia#2009
… be done from cmd.exe (don't need different shells) Closes eclipse-theia#1614 See also eclipse-theia#2009 Signed-off-by: Adam Retter <adam.retter@googlemail.com>
!!SQUASH ME Signed-off-by: Akos Kitta <kittaakos@typefox.io>
not sure, how relevant this is. I've pinned them, as a freshly created yarn.lock pulled some then-latest dependencies which were incompatible. afair it was related to webpack. |
@kittaakos fyi, I've tried this in linux workspace, and I could resolve the build issue by bumping these versions dependencies:
dev dependencies:
not sure about a) other platforms, and b) tests. |
Thanks, I know. Here is the PR for it: #3768. |
Are there any plans to support this soon? The latest version of VS Code (1.30.x released in February) says
It seems that this would have impact on the move toward a plug-in model (vs extensions) for Theia and running VS Code extensions out-of-the-box. If the extensions start using Node.js 10 APIs and Theia can only support Node 8, that might cause some extensions not to run. As far as I know, there is no shim layer for different versions of Node. So once the extension uses Node 10 API, you can't easily provide a backward version with Node 8. |
Co-authored-by: Alex Tugarev <alex.tugarev@typefox.io> Co-authored-by: Akos Kitta <kittaakos@typefox.io> Signed-off-by: Jan Keromnes <jan.keromnes@typefox.io>
Co-authored-by: Alex Tugarev <alex.tugarev@typefox.io> Co-authored-by: Akos Kitta <kittaakos@typefox.io> Signed-off-by: Jan Keromnes <jan.keromnes@typefox.io>
…yor. Signed-off-by: Jan Keromnes <jan.keromnes@typefox.io>
Co-authored-by: Alex Tugarev <alex.tugarev@typefox.io> Co-authored-by: Akos Kitta <kittaakos@typefox.io> Signed-off-by: Jan Keromnes <jan.keromnes@typefox.io>
…yor. Signed-off-by: Jan Keromnes <jan.keromnes@typefox.io>
….x.x`. Closes eclipse-theia#2009. Signed-off-by: Akos Kitta <kittaakos@typefox.io>
….x.x`. Closes eclipse-theia#2009. Signed-off-by: Akos Kitta <kittaakos@typefox.io>
Help wanted. See: #3358 (comment)
The text was updated successfully, but these errors were encountered: