-
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
Installation failed with LTS Node version12.16.1 #7349
Comments
Yeah, an error says that it is not supported. Please use Node 10 instead. |
ok will do in a docker Image, actually I would hope for a release soon for the latest Node JS version...No ? |
We align with Node.js version of currently used Electron as minimum. Till we don't upgrade to new version of Electron I don't think active committers will invest into supporting latest Node.js. Someone from the community could invest time and look how to include Node.js 12 in supported range without breaking the minimal version if it is critical for them. |
VS Code extensions are allowed to use Node.js 12 API. It can become a problem if some will do. |
We should support Node.js 12. |
Closes #7349 Signed-off-by: Akos Kitta <[email protected]>
Updated the `@babel` dependencies to fix babel/babel#11216#issuecomment-634460665. Closes #7349 Signed-off-by: Akos Kitta <[email protected]>
Updated the `@babel` dependencies to fix babel/babel#11216#issuecomment-634460665. Closes #7349 Signed-off-by: Akos Kitta <[email protected]>
- Updated the `@babel` dependencies to fix babel/babel#11216#issuecomment-634460665. - Pinned the `node-abi` version in the `resolutions` to support latest `electron`. - Added a `preinstall` script to warn about Node.js version. Closes #7349 Signed-off-by: Akos Kitta <[email protected]>
- Updated the `@babel` dependencies to fix babel/babel#11216#issuecomment-634460665. - Pinned the `node-abi` version in the `resolutions` to support latest `electron`. - Added a `preinstall` script to warn about Node.js version. Closes #7349 Signed-off-by: Akos Kitta <[email protected]>
@kittaakos so that issue can be closed ? |
No, not yet. Here is the PR: #7968 |
- Updated the `@babel` dependencies to fix babel/babel#11216#issuecomment-634460665. - Pinned the `node-abi` version in the `resolutions` to support latest `electron`. Closes #7349 Signed-off-by: Akos Kitta <[email protected]>
- Updated the `@babel` dependencies to fix babel/babel#11216#issuecomment-634460665. - Pinned the `node-abi` version in the `resolutions` to support latest `electron`. - Use Node.js 12.14.1 for Gitpod. Closes #7349 Signed-off-by: Akos Kitta <[email protected]>
- Updated the `@babel` dependencies to fix babel/babel#11216#issuecomment-634460665. - Pinned the `node-abi` version in the `resolutions` to support latest `electron`. - Use Node.js 12.14.1 for Gitpod. Closes #7349 Co-authored-by: Anton Kosyakov <[email protected]> Signed-off-by: Akos Kitta <[email protected]>
- Updated the `@babel` dependencies to fix babel/babel#11216#issuecomment-634460665. - Pinned the `node-abi` version in the `resolutions` to support latest `electron`. - Use Node.js 12.14.1 for Gitpod. Closes #7349 Co-authored-by: Anton Kosyakov <[email protected]> Signed-off-by: Akos Kitta <[email protected]>
This is great, thank you! Any chance of a release so that we can test it? |
I think we have a release scheduled this Thursday, or you can use the |
@kittaakos We did some experimentation with the last release version on Node 10 and Node 12. We found that it would build already for Node12 on Linux, but not on Mac. However, regardless of the Node version we found that to get it building with Python3 (as opposed to Python 2) we had to force it to use the latest npm-gyp. This was especially relevant for macOS Catalina, see - https://github.com/nodejs/node-gyp/blob/master/macOS_Catalina.md To do that we had to add a
Before you do the next release, I think it might make sense for You can see our various Linux/macOS Node10/12 Python2/3 builds here: https://travis-ci.com/github/evolvedbinary/fusion-studio-extension/builds/176406238 |
I haven't had a build issue on macOS. What's the error? Also, please share a repo, or at least a
We still need Python2 as far as I know.
Sounds good to me, but I won't have the time to change anything wrt the
We have the next release on 30.7, next week. |
Here is another issue related to the current |
@kittaakos Further info:
Sure, it was linked vai Travis, but you can find it directly here: https://github.com/evolvedbinary/fusion-studio-extension/tree/ci-test-adam
It is as in the Travis CI results page I linked to. This is the error when trying to build against Node12 on macOS (both 10.13 and 10.15):
As per my Travis CI results - it builds fine with Python 3, but ONLY if you update to the latest node-gyp.
Absolutely. What's the process? Just send a PR? do you have automated CI etc to check it for me? |
@adamretter, I have started a macOS build with Node.js: https://travis-ci.com/github/eclipse-theia/theia/jobs/363327516
Adding
So if I understood you correctly; your goal is to be able to build with Python3 on macOS. For that, we need to increase the
Great.
https://github.com/eclipse-theia/theia#contributing
Yes.
Yes. |
I want to build with Python 2 and 3 on all platforms. We have that working here by updating the node-gyp version. I also want to be able to build for NodeJS 12 as well as NodeJS 10. Using the latest release, i.e. before the PR #7968, my experience is that NodeJS 12 fails on macOS, I will now test with the latest HEAD code. I will send a separate PR to increase the number of your Travis CI jobs to cover that platform too. |
Sounds great!
OK. Note, we will drop Node.js 10.x soon. #8184
Watch out, that might get rejected as we do not want to unnecessarily increase the build time. |
This reverts commit 9afc819.
This reverts commit 9afc819.
This reverts commit 9afc819.
This reverts commit 070417c.
Description
Reproduction Steps
following the https://github.com/eclipse-theia/theia/blob/master/doc/Developing.md#quick-start guid fails with
error @theia/[email protected]: The engine "node" is incompatible with this module. Expected version ">=10.11.0 <12". Got "12.16.1"
OS and Theia version:
OS is Ubuntu 18.04
Node Version is 12.16.1 (LTS)
Git cloned latest theia version
Diagnostics:
no further analytics requiered thought you want see the problem with old docker images
The text was updated successfully, but these errors were encountered: