nvm | Node Version Manager - POSIX-compliant bash script | Runtime Evironment library

I am trying to create a new React app using this command on Windows using Node 16.14

npx create-react-app my-app

But it fails with this error npm ERR! Unexpected token '.'

From the log, this is the stack trace:

I just installed the latest version of node(16.8) using nvm and angular/cli(12.2).

But when i run ng --version

It shows the following:

Warning: The current version of Node (16.8.0) is not supported by Angular.

I tried to downgrade the node and installed node 14.15 but ng is not working anymore.

Should i ignore the warning and use node 16?.

Why is ng not working with node 14.15?.

PS: I am using nvm to manage the different node versions

this is the log when vscode install vscode-server in host

i found that it got vscode-server commit id as follow log:

I have installed nvm using brew. After that, I installed node version of 16 through nvm and check the current version using node -v to see whether the node is working properly. However, when I install version 14 or any other previous versions and runs node -v, it gives this "zsh: bad CPU type in executable: node" message and I have no idea what to do about this, though, installing node v17 and running node -v works as expected. Below are the snippet of the said commands.

My CircleCI file is provided:

I am using my corporate's laptop and am a new mac User (used Ubuntu before) :

• OS: macOS Monterey Version 12.2

There are two accounts, administrator and mine - I don't have sudo rights. To install homebrew without administrator rights, I followed this Installation.

To install the node - I used brew install node. Both node -v and npm -v were working. When I restarted the laptop, I cannot find node/npm.

On running $ node -v, I get -bash: node: command not found (I changed my default terminal from zsh to bash and the output is the same for both of them)

I tried this solution but couldn't find nvm in the system. Am new to mac and I believe nvm is some kind of package manager like homebrew so this solution is not applicable to me (correct me if I am wrong).

How can I install things in my system without sudo rights and keep them permanently(like node)?

EDIT:

• (After adding brew to the PATH) On running - brew list|grep node, I got - node

• $ echo $PATH gives /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/parthkapadia/homebrew/bin

EDIT2:

• Adding brew to path solved the issue, now I can even access node and npm (even after restarting). I used this site to add homebrew/bin to path (in zsh terminal)

I'm trying to downgrade Node's version via nvm on Windows 10, but I can't get it working:

C:\projects>nvm use 16.13.2 all
Now using node v16.13.2 (64-bit)

C:\projects>node -v
v17.4.0

(I nvm install and nvm use 16.13.2 on both 32 and 64bit; also tried to restart the command prompt, but always showing v17.4.0)

Just got a new M1 Mac Mini and I have been having trouble running my Android projects.

I'm using Android Studio (Bumblebee), JDK 11 (tried 17 as well), and Gradle 7.3.

When I try to run the project from AS, it builds fine and then gets stuck on "Waiting for target device to come online" and eventually times out.

If I try to run the emulator again I get a message that the device is already running, including a path to a lock file.

However, I've found that if I run the emulator manually from the CLI, the emulator does open, at which point I can get AS to run the app on said emulator. So the problem is apparently just that AS can't open the AVD.

Command line output when running emulator via adelphia$ emulator -avd Pixel_3a_API_32_arm64-v8a:

I've been looking for the answer to this for a good solid week now, with no success. I've looked at every StackOverflow post, every article from Google and every related Github issue I could find. Most related errors seem to be older, so I'm wondering if my issue is slightly different due to me being on macOS Big Sur.

The issue: When I try to run yarn install in my local repo, I receive an error related to node-gyp and a python executable that is unable to be found. Here is what my terminal shows: