image: https://i.stack.imgur.com/bpDuM.png
I just installed EasyPHP Devserver, it would enable you to access PHPmyAdmin clicking on module at the bottom of the page, the problem is that in order to start those modules You must start the Database and HTTP before.
Http works, but when I click on Database it doesn't do nothing.
I've also tried to use Xampp, but neither this works, maybe my pc has some problem with virtual ports...
it looks like it's not a virtual ports problem !
I started the development with easyphp, but after that I preferred to use WampServer, and even more linux debian.
if you want to work with wamp, don't forget to install Visual Studio :)
Related
I started a new developer role a few days ago and made some environmental changes to adapt for work. Since then, my hot reload/fast refresh has just stopped working entirely. Changes don't show up even if I refresh the page manually. Only shows changes when I stop the dev server and restart it with 'npm run dev'. The triangle indicator at the bottom right should be active, showing active reload of the window (this no longer shows up consistently either, and if it does the page gets reloaded, but alas the proposed changes aren't visible)
Context:
It has this effect on all NextJS and react applications of mine. Even running a basic project template off the NextJS examples page shows no hot reload working.
I researched this issue and it seems wrong imports (e.g. importing components using lowercase or files in the pages directory being capitalized) can cause this, but I combed through the code and can't spot any issues (of course, I could be missing it but my codebase is over 300 files).
Service workers in the background can cause issues, but I cleared my browser of all of them to be sure and it still doesn't fix it.
I installed ngrok for tunneling for work purposes and docker-compose to handle the work dev. environment.
Made sure I'm using the latest Next version. Even deleted node_modules and ran npm install. Deleted .next and the out folder and still no luck.
Anybody have any ideas or clues to what I should try next? Is it related to the stuff I installed for work? Something related to VS code or WSL2? Seems so puzzling it kind of just happened overnight. Thanks for any insight or advice!
System information
OS: Windows (WSL2 virtualization for VS code)
Browser: Chrome
Version of Next.js: 10.0.3
Version of Node.js: 14.8.0
Deployment: npm run dev for development work; amplify publish for AWS hosting
The problem is with WSL2. I use WSL2 inside VS Code; which is a big performance upgrade in the Linux environment. The problem is WSL2 is actually in a 'virtualization' and thus cannot send information from VS Code AND the browser (localhost:3000) at the same time.
It's a big issue they are working on and there is no fix yet for it. That's why fast refresh doesn't work because localhost is not receiving the changes being made. Either proxy through or revert back to WSL1 https://github.com/microsoft/WSL/issues/4769
Solution provide by OP on question section
Add a .env file or a .env.local file to your root and put this line on it:
WATCHPACK_POLLING=true
Now, restart your server.
Thanks I encounter the same issue with WSL2. I just switch to windows terminal and it works.
If you run Poweshell as administrator and run
wsl.exe -l -v
This will give you th eversion of wsl your distros run on.
I am personally using Ubuntu, and this is the output
Ubuntu Running 2
docker-desktop Stopped 2
docker-desktop-data Stopped 2
To switch to wsl 1,
Run
wsl.exe --set-version Ubuntu 1
and if you wanna switch back,
run,
wsl.exe --set-version Ubuntu 2.
This worked for me.
In my react projects, I just add in my .env file at the root project folder the values
FAST_REFRESH=false
CHOKIDAR_USEPOLLING=true
and it works! enjoy!
The problem is with WSL2. I use WSL2 inside VS Code. But React JS and Next JS projects don't auto-reload. So, add a .env or .env.local (recommended) file to your root and put these lines on it:
WATCHPACK_POLLING=true
CHOKIDAR_USEPOLLING=true
Now, restart your server.
I am connected to the same network my device and PC , how can we fix this error ,
After restarting it gives the same error with :
Switched to a LAN URL because the tunnel appears to be down. Only devices in the same network can access the app. You can restart the project to try reconnecting.
on my device it says
Tunnel packager ....exp.not found
I am running on windows btw;
Thanks
Expo and react-devtools do not go together. So if you are using react-devtools, you must uninstall it. This worked for me:
npm uninstall react-devtools -g
But I noticed some other people were successful with this here.
npm uninstall react-devtools --save-dev
This is mostly because your firewall is blocking it. Verify by shutting off the firewall
Try running the ngork.exe in the background.
You can download ngork at ngork
Tunnel uses ngork. I faced similar issue and running ngork at background solved me the issue.
Am not sure how it fixed the 'Error starting tunnel' issue.
Hope I fill find it soon.
I solved this by examining my order of operations.
Other people at my workplace had managed to set the project up but for some reason I ran into this error.
I was using VSCode debugger and figured out that the emulator needed expo to be open and the project to be open within expo on the simulator before tunnelling was successful. I was attempting to run the debugger without actually opening the app.
this usually happens when you have an inconsistent internet connection. you can try restarting your wifi/computer & restarting xde. if that doesn’t work, you can try using a different network to connect to the internet. a last resort is connecting your device to the LAN and strong text running from there
In my case, somehow expo was unable to install #expo/ngrok library (that it uses internally to create a tunnel) when I click on tunnel option.
You can solve the issue by installing the library globally using npm and restarting the expo metro bundler with expo start.
npm install --global #expo/ngrok
This can also happen if you are using a VPN. Turning it off my VPN worked for me.
So, I am using WebStorm to develop an React app with webpack, usually I just run webpack-dev-server in the console, the server is at port 8081 and I open the browser, visit localhost:8081//build and all works with hot reload.
Today I want to debug deeper into the code with debugger in WebStorm, I never use break points before, so I went to this page https://blog.jetbrains.com/webstorm/2017/01/debugging-react-apps/
Though I did not install create-react-app, because my project is not generated by the module, I created project manually with webpack.config.js and package.json, I do not know how to generate a existing project.
Second, Instead of run npm start as the instruction, I also passed this part because I think web-dev-server is already a server, I do not need another one.
Then I followed the instructions from here, created a debug configuration with an url of "localhost:8081/build" as there is the webpack-dev-server location.
At last I tried to set "debugger - built-in-server - port" to 8081, I also installed JetBrains IDE Support addon for Chrome and tried to set the port to 8081 either. But WebStorm told me that the port is not free and also the addon on Chrome toolbar now is grey.
Then I thought that the addon port and debugger port is not associated with webpack-dev-server, only the debug configuration is associated, but these thoughts are all guesses, because I really do not understand.
At last I run debug, the app index page is opened and it said JetBrains IDE support is debugging, I modified any file and saved it would hot reload, console in WebStorm showed result as in Chrome console, seems all works great, except breakpoints, they are all ignored, like they were not there, in the debugger tool window in WebStorm, the Frames window shows "Frames are not available", the Variables window shows a blue round icon followed by "Connected to JetBrains Chrome Extension" and that is all, none variable shows there.
I am sorry I did not understand both WebStorm debugger and breakpoint debugging well, this was my first time I do not know how to get stuff together.
Should I use create-react-app explicitly to generate a project (please no), or is there a way to make all this working?
At last I tried to set "debugger - built-in-server - port" to 8081, I
also installed JetBrains IDE Support addon for Chrome and tried to set
the port to 8081 either. But WebStorm told me that the port is not
free and also the addon on Chrome toolbar now is grey.
Please set it back to default - port specified there is a port the IDE is opening on start for debugging/serving static files, it has nothing to do with the port of the server your application is hosted on
seems all works great, except breakpoints, they are all ignored
you need to make sure that the sourcemaps are generated properly (devtool: 'source-map' is the most preferred option) and (probably) specify the remote URL mappings in your debug configuration (check https://blog.jetbrains.com/webstorm/2017/01/debugging-react-apps/, 4. In WebStorm 2016 (.1, .2 and .3) section for some hints).
If it still doesn't work, please create a support ticket to get the assistance on setting up the debugger
I made some fixes for my App and wanted to try it out today on my iPhone and now I can't install it on the device anymore. I'm getting the error "Unable to Download App" on the phone.
I haven't changed anything on my Apple Developer Account and yesterday everything was working fine. Is this a known bug and does anybody know how to fix this? My iPhone is of course registered and I also did the "iOS Certificate Wizard" and built it again but it didn't work either.
Edit: So I was able to install the app after doing the complete Certificate Wizard again with also overwriting everything (which I had not done before), but now I made another build and I can't install it again! Do I really have to do the Wizard thing every time I send a build now?
Are you trying to install a distribution build on top of a development build, or vice-versa? If so, uninstall the existing app first.
I'm using React Native v0.35 after upgrading from v0.26. I can no longer use the dev server on my device like I used to. When it builds to my phone, connected on the same wireless ip as my macbook, it builds from a pre bundle instead of the server. I used to be able to just set the ip in the app delegate, but that's no longer an option. I just want to be able to develop on an actual device.
You can try few things -
Make sure you have set debug server host and port on device.
https://facebook.github.io/react-native/docs/running-on-device-android.html
https://facebook.github.io/react-native/docs/running-on-device-ios.html
Restart server
npm start
or
npm start -- --reset-cache
Re-install app (delete and install)
For anyone who is seeking a solution to this problem:
The issue was that if you are developing on ios using a macbook, the code that governs the auto ip detection fails to pick up your machine's ip, so it defaults to the pre bundled package. In order to resolve this (for versions >= 0.29 && < 0.36-rc.1 - which already includes this patch), open up your node modules directory, find the react-native directory, then open that and find the packager directory. In packager, there is a file named 'react-native-xcode.sh', open that up. Then, find the code snippet and add the three lines of new code from here. After that, rebuild your app and restart your packager. The dev server should now load.