I just purchased an Asustor AS3304T and the app central offers
to install a pretty old version of Node.js (10.13.0.r4.0.4)
I also have a few Raspberry pi devices and have been writing
some Node.js utilities using version 16.13.2.
Since I am not sure if I used features not supported by 10.x
I would prefer installing same or more recent version of Node.js,
possibly the lates LTS version: 16.18.9.
I use some Raspberry pies, but I am not a linux expert.
Just want to know if it can be done without causing problems
on the Asustor system.
I have searched a long time and the lonely solution i found is to install Entware from App Central.
I suggest to remove first the Nodejs app before installing the one provided by Entware.
Once done just
opkg install node
opkg install node-npm
and you will get node v16.16.0 and npm 8.11.0
Related
Im using a linux laptop 32bits and i wonder if there is a way to install nodejs version >=14 ?
Im trying to use React on VSCode and when i try to start a project it tells me i need Node 14 or higher
saberx#saberx:~/Documents/react$ npx create-react-app miapp
npx: installed 67 in 11.768s
You are running Node 9.11.2.
Create React App requires Node 14 or higher.
Please update your version of Node.
i searched on internet but cant find a way to install a higher version of nodeJs on my linux 32bits
Unlikely, Node 10 removed offical linux x86 builds (32bit).
There were unofficial/untested builds up to v12.16.2 but they ended there. I would guess they went from "unsupported" to "not possible".
I am building a sample application in which I need to use Node Version v9.11.2 and npm 4.0.0. Currently I have Node Version v16.4.0 installed on my system. I tried to install the specific version by uninstalling the latest version and installing version 9.11.2 from official website
Problem: The problem is I can uninstall the latest version without any problem but when I try to install older version(9.11.2) the command gets opened and it does nothing. I also tried to install the older version using cli commands ie. npm install -g node#9.11.2, it installs the version but on checking the version using node -v, it still shows the latest version(16.4.0)
Below are the screenshots for better understanding
Installed version 9.11.2 but showing 16.4.0
Any Solution please ?
Is using docker a possibility? If so you can simply get a docker image of the required version and use if from there.
Another way is to use NVM which is a really useful tool to manage nodejs versions. I'm including their github repo for your convenience:
https://github.com/nvm-sh/nvm
A good option is to use NVM: https://github.com/coreybutler/nvm-windows (Windows) or https://github.com/nvm-sh/nvm (unix, macOS). With NVM you can enable different versions of node on the same machine and switch from one to another, usually it takes care of managing the installed packages and adding them to its own management system.
I am quite new to NodeJS and am planning to upgrade NodeJS version for my current project. The most recent NodeJS LTS is installed using NVM.
I need to keep switching between the current LTS that i am using and the new LTS that has been installed. I understand that i can do 'NVM use' for this purpose. npm-shrinkwrap.json is being used to lock down the npm package dependencies.
I am planning to follow the below approach both in my dev machine and build machine;
Is it okay? If not, please suggest a best approach.
nvm use latest_LTS
Update the package.json to pick the version which is supported by
latest_LTS
npm install
generate testing_build
Whenever i need to generate a build for current release (with the previous LTS NodeJS)
nvm use currently_used_LTS
clear the node modules
npm install (Release npm-shrinkwrap.json)
generate release_build
Thanks
In theory that should work.
However have you considered the option of just doing a point release for the current release_build that does nothing except version-bump node?
You may find (after re-running your tests) that the latest version of node is backwards compatable with release_build (or only requires minor fixes), and you can simplify your life by porting everything to the latest node version, rather than constantly switching
I tried reading the official manual and two books, but the chage in versions is too large, even the directory sturcture is off.
I tried running meteor bundle --release 1.0.0
no luck
what is the first windows version of meteor, i shold downgrade to?
According to this: http://info.meteor.com/blog/meteor-11-microsoft-windows-mongodb-30
Meteor supports development on windows as of version 1.1
You have to have at least windows 7 installed. I would recommend that you upgrade your version of meteor to 1.1 or greater by running npm update meteor. If you want to use the first version of meteor that supports windows you can run npm install meteor#1.1
I just installed the current version of node (3/14/16) 4.4.0 directly from Node.js via a Mac Package (the new suggested way, previously I installed via Homebrew).
I'm curious if anyone knows why the package ships with npm version 2.14.20, the book I'm going through suggests updating npm manually with the command
sudo npm install npm -g
The version I see is now 3.8.1, that's quite a large difference hence my question, is it safe/smart to be this far ahead of what Node.js is officially putting out with their Mac package file?
EDIT:
It appears it's common for Node's recommended v4.x install to come with npm 2.x, the question that remains is, will there be any negative side effects of using the newest npm but an older version of node?