i'm having trouble developing with Nuxt3, the problem is that sometimes edits in the code are not visible, it seems that Nitro caches something and I need to restart the server in order to see the updates. The most effective example is when I console.log something, then i remove the line, but the log still get printed after I reload the page. Any tips?
Related
So, I'm building an application with Vuejs and after we finish her we decided to finally build for production. Everything worked just fine while building and etc, but when the application was really being hosted, we noticed some issues that we do not saw while on localhost (development and production).
I'm saying this after a lot of tests and researches about it because first, I thought that the problem was after building to production but we tested another way to host and it's not apache that is causing this issue and I really think that is not the code either. Anyway the problem is when we first access the application our login page is the first that you can see and it works just fine at the first access but if the user refreshes the page for any reason the page loses all her CSS because the route /auth/login goes to /auth/login/ and after some tests I can confirm. That bar that is added at the end of the route makes the page lose CSS.
This problem we solved by adding an exception on our .htaccess (we know that this is not that best practice but anyway) after this solved we saw another problem: when we click on a link for example /auth/login?token=12334567890 the token param simply disappear and the user is automatically redirected to /auth/login. So we think that maybe these two problems are related because when we first access and log in everything inside the application works as it should, these two problems are only occurring on our login component. My question is what is causing this problem only on this page? It's a vue-router that is causing?
A bit of context (I have been stuck on this for a few days now):
The first screen on my Ionic 4 app is the login page. Once I logged in successfully, everything works fine. Then, when I log out & log back in, the app just hangs. There is no error showing up on the console. So, my question here is, how can I debug to find out what is causing the app to hang half way using it?
*It hangs in browser mode and when it is running on android.
In order to debug your app step by step I recommend using chrome developer tools.
First you will have access to your source code, therefore you can put breakpoints at any position you want.
You can open this window by inspecting your page and selecting the source tap.
To locate the problem you should have an idea about Ionic Page Life Cycle
,
If none of the above works you still have the possibility to console log the code that you want to verify, also the template can cause such an issue if you have for example an infinite *ngFor or something that prevent the template from loading.
I have an odd problem. My Web-app is not available on every 10th call or so, if i click refresh its again available.
If i keep hitting the refresh button, sometimes it shows me again that my Page is not Available. I'm getting HTTP Status 404.
Does anyone know where the problem is ?
There wasn't a error with my Code. I deleted the Web-apps from "work/cathalina/localhost" and restarted Tomcat and now everything is working fine.
After changing something in my website and uploading to the server, I don't see the changes in my browser upon reload. The website loads from cache. It gets reflected after I refresh the page twice or thrice.
I need help in figuring out what's wrong.
Did you cleaned your browser cache. Restart it. Clean cookies and reset your browser to fix it, This may a problem local to your own Laptop/computer, people who will be accessing your web must be getting updated content that you pushed.
I was wondering if anyone could point out what is causing the problem in the screenshot attached. It has happened a couple of times with different images. I can't see what is causing it.
The machine is my development machine.
I was hoping to post this on serverfault but I can't add the image I need.
Not enough info yet, so just some debugging steps.
Try uploading it to a different machine and see if you get these same messages.
Check you don't have any Javascript doing anything with image urls - to me it looks like some loop somewhere might be going 'wacko', but could be client or server side.
Use tail -F on it in the terminal and refresh the page to see if the appearance of those entries coincides with the loading of the page.
Edit: maybe also have Firebug/etc open when you refresh the page with their Network panels open to see if you really are sending those requests. Really just want to find if it's a client or server issue to begin with.