This app references Microsoft.WinJS.1.0, version 1.0.8514.0, found in your SDK, but you have a higher version of Microsoft.WinJS.1.0 installed on the target machine, 1.0.9200.20602. If you continue to run this application, it will run against the currently installed version, Microsoft.WinJS.1.0, version 1.0.9200.20602. Consider updating your SDK to match the version of Microsoft.WinJS.1.0 that is installed.
Related
I have been using node.js for some years on Windows (10/11) and it has never automatically updated from the version that I originally installed.
Over the last few days, I have noticed that the version I originally installed (18.10.0) is being updated to 19.1.0.
Uninstalling version 19.1.0 and reinstalling 18.10.0 keeps the installed version temporarily, but at some undetermined point in time it automatically updates to later version again.
I am perplexed as to why the installation is automatically being updated. In this case to an odd numbered node.js version which results in the message "Odd numbered Node.js versions will not enter LTS status and should not be used for production." during a build.
Has anybody else experienced node.js automatically updating?
Is it possible that something else may be forcing the update?
I'm on a Microsoft Surface Pro X (it features Windows 10 Home on ARM 64-bit processor) trying to install Node.js. I've decided to use NVM for Windows. I can successfully install and get NVM for Windows running correctly. To my understanding, I'm able to install different versions of Node (i.e. 16.16.0 and 16.13.1, for example, both LTS) as shown in below graphic. But when I try to run Node, I get the error "This version of C:\Program Files\Nodejs\node.exe is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher."
I am not clear on the why this is happening. Am I not downloading a version of Node that is compatible on my ARM 64-bit processor? I've read through several closed issues on the GitHub page but I haven't encountered someone bringing up this same error. I'm pretty confident it does NOT have to do with the integrity of my symlinks too, or my system environment variables. See below:
Your help and insight is appreciated. Thanks.
The Omnis docs state "node.js is embedded into Omnis Studio".
I understand I can check node.js version in terminal node -v, however this is the version on my machine itself.
How do I determine what version of node.js is bundled within Omnis Studio?
After installing it, you can go to the directory that contains Omnis' Node executable. On Windows, it may be:
C:\Program Files\Omnis Software\OS 10.2 31315\clientserver\server\remotedebug
Then you can run node -v from that directory. The latest version looks to be 16.6.1. (This may well be a different version from the global Node on your personal machine - for example, my global Node version is 14, which I get when running node -v elsewhere, outside of that directory)
The latest release notes also say that the Node version in Macs is also 16.6.1:
The version of Node.js released with the macOS version of Studio 10.2 is now V16.6.1
which supports node running natively on macOS on M1 machines.
When I try to run an application that uses node-webcrypto-ossl node module I get the error:
Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found.
Obviously node-webcrypto-ossl requires an older version of glibc.
The version of glibc installed on my machine is 2.33-5. I've tried downgrading my glibc but ended up with a broken system (fixed it already).
How do I resolve the issue?
Obviously node-webcrypto-ossl requires an older version of glibc.
No. GLIBC is backwards compatible: applications built against older version continue to run fine on newer GLIBC versions.
Your problem is the opposite: you have an application linked against GLIBC_2.32 trying to run against an older version of GLIBC.
The version of glibc installed on my machine is 2.33-5
The application is not using that version; it's using some other GLIBC.
The problem was that I was trying to run my app in docker ...
That's one way running against older than expected GLIBC could happen.
I need to update PHPMailer on few servers if any old version was installed.
How to check installed version
How to update it to PHPMailer 5.2.20 (for example)
It depends on how you installed it. If you're using the recommended method of using composer, then a simple composer update will get you the latest version. Your composer.lock file will show you which version you currently have, or you can open the VERSION file which will show you the version number you've got - or if you have a very old version that predates the VERSION file, look in the source files instead - they will also say what version they are. If you've installed it manually, just download the latest version from Github and replace your current version.