It’s very annoying having to reload forge tunnel while testing the UI;
It doesn’t happen on every project; But if I knew what was different about this one I would have fixed it already.
Any ideas
Hey Owen,
I haven’t seen that before, have you tried running it in debugging mode to get more information about what is happening?
Cheers,
Mel
Tried
npx forge tunnel --verbose
But I don’t get any more information; Is there a better command to use?
I can confirm that it happens both in Chrome and in Firefox
Hey, I have the same problem here!
Using UI KIT the forge tunnel goes into loop, I have the same import { example } from ‘./example’; logic on few .jsx files.
After I added that forge tunnel went looping.
It would be great if you can take some video recording so that we can know more on how it happens. Thanks a lot
The problem still exists. @KhanhNguyen has this ever been addressed?
Hi all
I’m hitting the same issue: Forge tunnel gets stuck in an endless “Bundling → Reloading code → Running forge lint” loop when starting tunnel and also when editing a resolver function. This makes the dev cycle very slow and frustrating. Same behavior when running with --no-verify.
Environment:
OS: Windows
IDE: IntelliJ IDEA
Node.js: v22.x
@forge/cli: latest
App type: Custom UI (Vite dev server)
Project layout: frontend under ./static/frontend, backend in ./src
Symptoms Forge tunnel repeatedly prints:
=== Bundling code…
✔ Functions bundled.
Reloading code…
=== Running forge lint…
Listening for requests on local port …
No issues found.
…and keeps looping.
I tried ran a file watcher in parallel to see which files change:
npx chokidar-cli ‘**/*’ --verbose
I don’t see any repetitively changing files while the tunnel loops.
I tried also to add .forgeignore and nothing append
Observations:
Even with the watcher showing no file changes, forge tunnel still loops.
The loop also occurs with --no-verify.
Questions:
Is there a known issue with Forge tunnel’s file watching?
Does forge tunnel fully honor .forgeignore for its watch on Windows?
Any recommended flags or configuration to avoid these loops?
I am experiencing the same issue.
Windows, cli@latest, App type: Custom UI (Parcel)