4.3.0 update on MacPro Trouble installing xcode command line tools

After upgrading to 4.3.0 and re-opening I opened up a test folder and chose “System Check”.

First the message that COMMAND LINE TOOLS IS CORRECTLY INSTALLED.

BUT CONTINUED ERROR MESSAGES ABOUT XCODE COMMAND LINE TOOLS NOT LOADING DUE TO “NETWORK PROBLEM”

THIS MESSAGE SHOWS UP TWICE AND I GIVE IT ONE MORE SHOT TO INSTALL THE COMAND LINE TOOLS.
NO APPARENT SUCCESS.

SO, I SHUT DOWN AND REPOPEN WAPPLER 4.3.0 AND GO TO “SYSTEM CHECK”

MY NEXT “OKAY, INSTALL THE CLTOOLS” BRINGS THE FOLLOWING –

And now 15 minutes later –

I’ll let you know what happens next . . .

So, after following the insistence of Wappler 4.3.0 update for my Mac I have apparently installed the CLI which installed Homebrew, which I did NOT want in the first place.

Then Wapper’s System Check reports OLD VERSION of Node.js detected !
And apparently I have to go to the terminal and install brew so that I can get a new nodeJS –

So, on my MacPro I’ve followed the Brew instructions to update NodeJS

while having a pre-existing Project open.

At this point I know I’m probably installing a global node.js environment at the base of my machine’s node and other development services that would apply everytime I want to spin up a node server on my computer.

As opposed to a Wappler server installation meant to spin up for any Wappler project in my global Wappler environment.

I’m guessing at this point.

Then my Wappler terminal shows me these reports –

I continue installing Homebrew even though my earlier status showed Homebrew installed when I used the Wappler terminal.

I see that now the system detects the previous installation of node.js.
And that those files are “read only” even though I am logged in as Administrator.
So, I am in an incompleted mode of Node installation .

This all kicked off because my Wappler 4.0.3 System Check indicated I had a need for updated xcode command line tools.

What would be a recommended approach now from you Wappler NodeJS experts?

Thank you!

You should allow Wappler to install Homebew, otherwise it can’t install node for you.

If you don’t want that you would have to the NodeJS site and install NodeJS manually.

As for the Xcode Command Line tools installation - well we just kick in a regular Xcode command from Apple that does the installation and progress, so if there are problems or delays it is probably due to slow connection or something with the Apple servers.

Just a question, because it looks similar to an issue I had a little while ago…

Have you recently performed a migration from an Intel Mac/MBP to an Apple Silicon one?

No, to the migration question.
My issue is probably because after setting up Wappler in my Intel MacPro 2015 I was learning the terminal and installed node.js at the root of my MacPro Adminstrator path

Apomaxxs-MacBook-Pro2015:~ apo2015$

I have a separate setup on my MacPro Intel 2020 which I’ll dare open up later when I have resolved things on my 2015 model.

Same for Homebrew. And other dependencies for a server environment to develop an app already well-developed on GitHub by another developer.

I don’t know how to correctly reconcile this with what Wappler detects on Server Check.
The sym link Wappler/Xcode terminal system check offers fails because permissions are read-only.

In one place I get the message that I have to update Node.JS to version 13.
In another Terminal window it’s happy with the Node.JS version 12.

My question now is how to Install one server environment that can be used by Wappler and also when I am using a non-node.js web browser to see rendered pages.
Or if I am taking a GitHub 3rd party open repository into my localhost server and using Visuall Studio to modify it.

Is there a tutorial or best practice on how to initiate a localhost node.js server for rendering these pages in a browser view while also setting up the best location for Wappler development sites?

I actually started saving Wappler site files in the same path as a Mamp server installation.
But I want to unsnarl this before I go on . . .