Worker generation issue: missing lookup constants + u is not defined in minified worker

[m2gi-mohamami]

Hi SDEverywhere team,
We are using @sdeverywhere/plugin-worker in a JS generation setup and are seeing recurring runtime issues in the generated worker(model fails to loas in some cases ).

Observed issues
• Some lookup data constants (_...data...) are present in processed.js but missing in final worker.js, causing runtime reference errors.
• In some generated SUM/LOOKUP expressions, [u] is used without a corresponding for (let u = 0; u < 8; u++), leading to u is not defined.

Current workaround
We currently use a local post-build patch script that:

• reinjects missing lookup constants,
• rewrites affected SUM/LOOKUP patterns to ensure u is defined,
• validates remaining [u] references heuristically.
  This workaround stabilizes runtime behavior, but we would prefer an official solution without external patch scripts.

Questions

1. Is this a known issue in compiler / worker plugin output?
2. Is there an official configuration to avoid this without custom patch files?
3. Is there a recommended clean integration point for safe post-processing of generated worker code?
4. Is a fix planned in upcoming versions?

Thanks in advance.
Best regards,

[chrispcampbell]

Hi @m2gi-mohamami, sorry to hear you're running into problems. I have never seen the first issue you mention (data definitions not present in worker.js); that sounds surprising. For the second issue, we had a couple related issues that were fixed a long time ago, but you might be hitting a case that triggers a similar issue but that we didn't account for in the compiler.

Is your project in a publicly-accessible git repository? If not, it would be great if you could either a) provide me access to the model (either set me up with permissions or just email me the project or at least the mdl) or b) help craft a small isolated mdl that reproduces each issue.

To answer your specific questions:

1. There are no known issues filed for either of your observed issues. We can file two new issues (since they sound like distinct issues) but I will need a way to reproduce them first, either (ideally) a small/constrained/isolated test case that reproduces each problem, or access to your model (from which we can derive a smaller/isolated test case).
2. No, but if you're not already doing so, you can use the postGenerate or postBuild hooks in a custom plugin in your sde.config.js file to apply your (temporary) patches/fixes.
3. It depends on the exact point that you need to apply your fixes, but you could use a postBuild hook in a custom plugin that is ordered after workerPlugin. But again, hopefully this is a temporary solution, since it shouldn't be necessary to edit the generated worker.js file except in some rare case like when there is a bug involved (like the one you are facing).
4. I will try my best to get fixes ready and published once we have a way to reproduce.