I have created a new react application using npx create-react-app my-app. I did this without any problem on mac os Majave, 10.14.6, my work computer. Using npm start, the web server and application starts as expected.
When I do the same on my home computer, running mac os Catalina 10.15, I am able to create the application, however, when I start it using npm start, it fails. There are serval suggested steps to fix the problem which I have followed but it still fails.
I suspect the server is 32 bit, which will not run on mac os 10.15 but have not seen any documentation. Is this supported on mac os Catalina?
I just tried to create a new react app using: npx create-react-app my-app. It worked perfectly. I then saw this message on the screen (see screenshot).
I then ran yarn start as suggested which opened a browser with the React website. Also tried with npm run start, also worked like a charm (see the other screenshot).
I am using:
macOS Catalina 10.15.1
yarn 1.19.1
npx / npm 6.4.1
node 10.13.0
Maybe check if you have the same versions and try again. Otherwise please be more specific and post the exact error message you see.
Related
I am using rush and trying to run rush install in a project I cloned from one of my company's repositories. But, it fails by throwing the following error:
The chromium binary is not available for arm64:
If you are on Ubuntu, you can install with:
apt-get install chromium-browser
Note: I'm using iTerm2 terminal for all this running on an Apple Macbook Pro having Monterey as the OS, powered by the Apple M1 Pro chip.
PS I tried to look for answers o'er the web and found this post but the answer doesn't seem to work for me.
As mentioned previously, this is due to the new M1 chips. I've been able to resolve the issue by using node v15. Could try nvm use 15 from the command line in your project directory.
I use Packages app to install an application and run a post install script that configures the Native messaging host. I require admin rights to for the installation. I had 2 main issues on macOS Sierra (maybe High Sierra too).
The native messaging host is a python3 script, I run command -v python3 on the post install script the to check if python3 is installed, if not the script exits with an error.
When I run the installer on macOS 10.15 (Catalina) everything works es expected (since Catalina comes with python3). I have installed the official python3 pkg and ran the installer again on 2 machines, one is on Catalina so no problem, the other is on Sierra on which the command command -v python3 fails always even though it runs perfectly from terminal.
I now check for python3 in 2 paths using ls /usr/bin/python3 (Catalina's python3) or ls /usr/local/bin/python3 (official python3) and it works perfectly on Sierra and Catalina.
Another issue, only on Sierra, I kept getting the error Unchecked runtime.lastError: Native host has exited. so I tried to run Chrome on debug to see what's going on and I was surprised to discover that the message has disappeared, but I kept getting if if I click to open the app, it works also if I just run open from terminal (keep in mind that everything works perfectly on Catalina). I have tried everything I could think of, I still don't understand what's going on. I have reproduced this issue on 2 other VMs Sierra.
the rights on the nmh script -rwxr-xr-x
Will provide any code you'll need.
UPDATE
See my answer, I will leave the question open as I am curious about the reason I get different behaviours on Catalina and Sierra
it looks like on Sierra Chrome can't interpret the shebang #!/usr/bin/env python3. I solved it by using sed after finding the right python 3 path.
When I build and run any project on Xcode, I face this error:
On the other hand, when I using command-line and install and launch the app by commands, I can see logs and everything is ok.
I did see other similar questions and I did try solutions like the clean project, build and reset and restart simulator and reinstall various versions of Xcode, but didn't fix.
My OS:
Mac Os Catalina 10.15.4
I removed some additional kexts from EFI partition, this problem solved!.
Thanks to Jeremy Huddleston Sequoia
I've just downloaded the latest Nativescript Sidekick. When I try to run it, I get the message that it is expecting:
"NodeJS >=8.0.0 <=10.5.0"
I'm using nvm, so I can switch node versions at will, but Sidekick appears to ignore this and pick up the latest (10.9.0 in my case). How does Sidekick detect the nodejs version? And how can I persuade otherwise???
After #GGarabedian confirmed that it worked with NVM for him, I played around a bit and discovered that Sidekick is looking for the NVM alias Stable.
So, by setting the alias to v8.11.0, Sidekick did work for me.
nvm alias stable v8.11.0
I have tested NativeScript Sidekick with the Node Version Manager and it appears to detect the currently selected Node version correctly. Can you verify if you have installed and selected a NodeJS version between 8.0.0 and 10.5.0 by running the node --version command in the Command Prompt?
Also, my tests were conducted on a Windows machine and it would be good to know if you are running on the same or different OS.
I've followed all the steps here https://console.developers.google.com/start/appengine?_ga=1.82598931.449716086.1415074596 successfully up to step 5.3. When I try to start the server:
dev_appserver.py appengine-try-python-flask
I get the following output:
-bash: dev_appserver.py: command not found
I'm on a Mac running OS X 10.10. Any ideas what I'm doing wrong?
I'm running Python 2.7.6.
It seems like you didn't correctly add the dev_appserver (and other GAE tools) to the bash.
Did you restart your shell(s) to pick up the new environment changes?
If you did and the problem still persists, you can try downloading manually the GAE SDK.
After that, open the GoogleAppEngineLauncher, and just click OK on 'Make command symlinks'. This will solve your issue.
It's all easily explained in the official documentation:
Download and Install the Google App Engine SDK