[V2] How identify my code is running in the "Generating bindings" phase after "wails dev" command

[funte]

How identify my code is running in the "Generating bindings" phase after "wails dev" command

[dosubot[bot]]

Hi @funte! I'm Dosu and I’m helping the wails team.

In Wails v2, user code does not run during the "Generating bindings" phase. This phase is handled internally by Wails as part of the build process, where it analyzes your Go code and generates the necessary frontend bindings, but it does not execute your application logic. There is no environment variable, flag, or hook set by Wails to indicate this phase from within your code—it's entirely separate from your application's runtime. If you need to perform custom actions during this phase, you'll need to handle them outside of Wails, for example, by using external scripts in your build pipeline. For more details, you can review the relevant implementation in the Wails source code (generate.go, dev.go).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[funte]

@dosu How explain this doc?

Bindings generation process runs your application in a special mode. If application, intentionally or unintentionally, contains an endless loop (i.e. not exiting after wails.Run() finished), this can lead to build process stuck on the stage of bindings generation. Please make sure your code exits properly.

[leaanthony]

It's lying - it runs whatever is in your main up to Run() then once it grabs the bindings it quits.