I have installed VS Code on a fresh load on Ubuntu. Im trying to start a new react native project with Expo and I want to be able to debug in VS Code using the React Native Tools extension. I had it set up on my laptop with ubuntu and it worked ok. Now running it on my PC when I click on Start Debug it runs for about 2 seconds and stops. Absolutely nothing shows up in the Debug console. Running Node 14.4.0. Deleted everything and ran expo init a couple times: no change. Anyone encounter anything like this before?
Related
I'm using VSCode with WSL. With the Remote WSL extension I'm opening my project in VSCode. I'm running my project (it's a react project) in WSL. First I can connect to my application on localhost:3000 but after a while my browser says that it couldn't connect to it. My project is running fine without errors. I've tried it with Chrome, Edge and Firefox (with and without extensions). Same thing. After a while it loses connection. If I run the project on my local windows it works fine. It used to work with WSL too just a few days before.
Brower connection error
My project running without issues
I've tried updating all of the WSL packages and reinstalling all of my VSCode extensions but it didn't help. Any idea what's causing this issue and how to solve it?
I am trying out react native on my M1 MacBook and I am getting this when I launch the Xcode IOS simulator.
I do not have any errors in the console and the QR code scan on multiple devices is working perfectly.
Here is what happens:
open and close
here is my console:
My console
Have you tried updating xcode. A while back I also experienced problems with xcode on mac and after updating xcode everything was working again.
I installed Cassandra and everything is working as expected.
I got the steps to install Cassandra from here
I've set up a React Native application that works fine with an emulator till I try to install the moment library to work with dates. This library won't even finish to install and then commands are not recognized anymore.
At the begining, everything runs correctly :
Then, installing the moment library :
Since the installation runs for ages, I did a Ctrl+C on it. Then the Metro and Android command won't be recognized :
However, these commands are still in the package.json :
From that point, the app is completely messed up. I have to erase everything and start all over again.
So? is it that npm packages cannot be used like in a regular React app? I don't understand what is going on here.
Thank you for your help.
I'm trying to do a fresh install of nextjs on Windows (see command line screenshot) using gitbash and latest nodejs lts version (16.14.2). When running npm run dev everything seems to be in order.
However, after browsing to http://localhost:3000, I receive this:
I looked at Fresh NextJS App throwing errors before any changes but the version in that issue is next 11.1.1 whereas current is 12.1.4. At this point I'm pretty much stuck. =\
Turns out it was an issue with Chrome extensions. I disabled all of them and no longer received the error. One by one I re-enabled all of them but never found the source. =\
I'm making a React application and I'm currently using Visual Studio to run the program and VSCode to edit the code.
When I used to save changes on VSCode, it automatically refreshed the browser with the changes I did. But recently it stopped working and now I have to make a manual reload (F5).
Here's what I've tried so far without success:
Updated both programs to their latest version.
Deleting the file and downloading it again from Gitlab.
In Visual Studio: Tools > Options > Environment > Documents cheked the boxes to detect changes outside enviroment.
Delete and generate again the .vs folder
Tried on a different browser
Tried making changes in Visual Studio
And so on ...
I tried with a similar app I built and that one was working fine and using the same properties.
There's currently two of us working on the project, but this issue only happens to me.
I recommend running the React from VSCode, using npm start / yarn start from command line in the directory.
Try changing something and see if the browser automatically reloads.