Thank you, have you tried it out?

This implies that _generated is true for consecutive runs, however I think that dart run build_runner build should create a new instance but I might be wrong

@Tienisto

Yeah, I did a few test runs on my project:

• Builds with dart run slang should be unaffected -- the changed builder is used only by build_runner.
• Clean build rakes through the i18n files and generates the full translation file.
• When source files are unchanged, I don't see build function being triggered at all.
• When source files are changed, I see the builder re-running on all .i18n.json files.

With the old version, I see the following:

The builder does attempt to rebuild, but the _generated flag is flipped when it processes the first file. Then it taps out for everything else. So, if I change the first file it happens to process -- it does update translations. However, if I tweak the 2nd or 3rd -- _generate has already been flipped to true and builder exits early.

With simple instrumentation, you can observe what is happening. I've set up these minimal repros on top of your slang/example, so you could test out both the current master and my proposed changes. The prints from the build function should be visible when you run dart run build_runner build, if you want to see class instantiation log add -v flag.

• This PR's changes with prints
• main with prints

Try running the build_runner with or without changes to source i18n files.

Aaaand now everything suddenly works for me without any fixes.
Let me figure out where I miscalculated and get back to you haha

No worries haha