-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nuxi dev
infinite refresh loop
#29
Comments
From what you've said, it sounds like this might be more helpfully dealt with in https://github.com/nuxt-community/tailwindcss-module. Or do you think this is a Bridge-specific issue? |
Hi @danielroe , |
Hey @danielroe, I have created a repository to illustrate the problem. To my surprise, this time the inifinite loop is there even though in other project I do not experience it with the https://github.com/DamianGlowala/nuxt-bridge-css-loading-delay-repro Please note the |
Also experiencing issues with this. What causes the issue for me is that the configuration syntax seems to have changed. You have to change this: // nuxt2, no bridge:
export default {
build: {
postcss: {
plugins: {
tailwindcss: {},
autoprefixer: {}
}
}
},
} to this: // nuxt2, with bridge:
export default defineNuxtConfig({
build: {
postcss: {
postcssOptions: {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
}
},
},
}) That's fine so far. Now the infinite refresh loop is gone. Issue now that postcss seems not to work quite right anymore. It doesn't pick up the .css file and therefore tailwind just doesn't work. My question to the authors of nuxtjs: Where would the best place be to create issues for this? (I am not using nuxt-tailwind, so not there).
|
Thanks @madebyfabian. Update: not resolved by that PR. |
Last days I been test the fb login sdk, but it doesn't let me use sdk without https, I notice of the infinite reload problem when change dev script to run it over https, first of all I thought that the problems comes from fb-sdk (maybe fb script check that is not a real ssl cert or somenting and it make a reload to prevent fraud), but after searching over hours with no results, finally I decide to start a new empty project and I got the same problem: // windows 10 terminal
Then modify the package.json scripts to:
And finally: |
I recently ran into this problem, but it seemed to occur when hot-reloading after changing the config file. Stopping and starting the dev server fixed it. Not sure if it's related. UpdateSo I found out what is making this happen, at least in my case. If I enter If I enter However, I'm not quite sure what to do yet to resolve this. |
(dockerized app) |
I have the same issue, and I'm not sure if it's related to this. But from what I can tell in my app it's the proxy-module that's not working properly. I'm proxying |
I have found a fix for this issue, at least for me. I was using a remote development environment, and Visual Studio Code only port-forwarded port 3000. For the vite-websocket, port 24678 is also required. |
I was proxying Nuxt in development mode on a subdomain and I faced the infinite reload issue:
However, accessing the server the app via IP address and port number worked. In my case the issue was caused by Cloudflare's cache. Disabling the cache fixed the problem. |
This one fix the problem for me! |
Yes!!! You saved my life, I used VSC in remote dev environment, it refreshes infinitely, and your suggestion is priceless! |
also solved it for me in docker-compose environment |
Thank you. You saved my ass. |
For me the problem was the |
Environment
Windows_NT
v16.13.1
2.16.0-27358576.777a4b7f
npm@8.1.2
Webpack
head
,srcDir
,css
,plugins
,components
,buildModules
,modules
,moment
,tailwindcss
,pwa
,i18n
,axios
,proxy
,router
,build
,alias
,server
,bridge
@nuxtjs/axios@5.13.6
,8n
,@nuxtjs/pwa@3.3.5
,@nuxtjs/proxy@2.1.0
,cookie-universal-nuxt@2.1.5
@nuxtjs/stylelint-module@4.1.0
,@nuxtjs/moment@1.6.1
,@nuxt/postcss8@1.1.3
,@pinia/nuxt@0.1.8
,@nuxt/bridge@3.0.0-27406801.569aaeb
Reproduction
As much as I cannot publicly share the repository containing the project's source code, I'd be more than happy to provide access through e.g. TeamViewer to one of the Nuxt team members.
Describe the bug
I have recently attempted to "experience Nuxt 3 features on existing Nuxt 2 projects" by following the instructions:
https://v3.nuxtjs.org/getting-started/bridge/
When running
npm run dev
(nuxi dev
), the project builds successfully, but is stuck in an infinite refresh loop, as shown on the below video:https://drive.google.com/file/d/1Ce0Qv67EvyBbucwgFj5pmAy5o5Y73RHD/view?usp=sharing
UPDATE
This is the piece of code that triggers an infinite loop:
Additional context
package.json
file content:tsconfig.json
file content:nuxt.config.ts
file content:Logs
No response
The text was updated successfully, but these errors were encountered: