I am new to Electron.
One of the biggest benefits of Electron is considered that it always comes with the latest versions of Node.js and Chromium.
But can I select which version of node js to use ?
You can't select which version of Node to use, however you can upgrade Node version as long as it is compatible with the current Electron's Chromium version.
Check this for farther information: https://electronjs.org/docs/development/upgrading-node
Related
Have multiple versions of Fabric runtimes on local machine (8.1, 8.2, and 9.0 series) which can be listed with:
Get-ServiceFabricRuntimeSupportedVersion
Have combed the Fabric documentation + web for anything about switching (changing) the SDK or Runtime version (effectively rolling back to an earlier installed version not the latest). Nothing. Anybody got an answer. Stopped investigating after trying:
Connect-ServiceFabricCluster
Unregister-ServiceFabricClusterPackage -Code -CodePackageVersion "9.0.1017.9590"
to back out version until I got to the one I want (8.2.1235.9590). But that fail with:
Fabric version has not been registered
Assuming this concerns only the current Powershell context. Start-ServiceFabricClusterRollback flops just like Unregister-ServiceFabricClusterPackage.
This might be very unhelpful, but I think the Supported Runtime Version is just which runtimes does the PS scripts support, not something about the local cluster.
The runtime you have installed is the latest one, so if you want to use an old one you have to uninstall the latest and find the bits for the old runtime and install that.
I am however, not entirely certain! It might be possible to switch runtimes, though it seems unlikely.
From the Control Panel choose Uninstall Programs and removed Fabric (6.0 SDK and Runtime). Restarted Windows (PC). Unclear if a restart is really necessary. Then opened the Web Platform Installer and through Spotlight searched for Fabric to click on Add. That put back 4.2.1235 of the SDK I needed. Done.
To my knowledge, the latest non-alpha version of the #ui5/cli and #sap/ux-ui5-tooling (as of 2nd March 2022 - version 2.14.6 and 1.5.0 respectively) are the ones to use.
However, I wanted to confirm as my organisation has multiple ui5 projects and so having a standardised version of the #ui5/cli and #sap/ux-ui5-tooling dependencies could prevent issues around bugs in tooling.
If the advice is just to use the latest non-alpha version, then I just need to update the dependencies regularly.
The versions you mentioned should be your choice to use in a productive environment.
The upcoming UI5 tooling 3.0 is not.
I don't think you will achieve the same version in every app because of the lifecycle.
The packages are fast paced and when u have a stable app deployed you will not update it every month I think.
I would not invest time to find the perfect tooling version.
We have a VSCode extension that uses node, but when I import it directly, it doesn't work because it has to be compiled using the Electron framework.
When I compile the module with Electron, I have no issues.
What is the difference? What does the Electron framework do?
Thanks,
Akhil
Electron ships its own, custom version of node and VS Code uses that to run extensions. The difference between Electron's node version and your node install doesn't matter much when executing JavaScript but native node modules must be recompiled to ensure they are built for the specific version of node electron uses.
This document on ABI stability in node covers some of the reasons why recompiling for different node versions is required in the first place
VS Code, just noticed I'm getting two different versions of Node.js from powershell, and About.
Because the version from vscode is 'the node version of vscode', you know the vscode is developed by Typescript.
And the version from powershell is your own node version you installed.
I want to create an MSI installer containing three apps. I will be releasing frequent updates to each app as I work through the list of feature requests and do bug fixes. The three apps are currently at versions 1.6.3, 1.6.12 and 1.8.1 respectively.
I was wondering what you guys can recommend for the version of the package. Should I:
Make the package version independent of the versions of the individual apps ?
Change the apps so they always have the same version as each other ?
Some other suggestion ?
Modify the package version each time the version of one of the apps changes. Then, you can look at the package version and know exactly which version of each app was being used.
Example:
Main version 1.4.1 has (1.6.3, 1.6.12, 1.8.1)
Main version 1.4.2 has (1.6.3, 1.6.13, 1.8.1)
Main version 1.5.0 has (1.7.0, 1.6.13, 1.8.2)
Main version 2.0.0 has (1.7.0, 1.6.14, 2.0.0)
So, if you're doing a minor version upgrade to one of your apps, the main application also goes up by a minor version number. Major changes to a sub-app result in the main app also getting a major version number change.