@sjkl can you check which version of the build pipeline you have running? 1.2.0 should fix the bug above. The error mentioned before happened only with compression (production builds).
You can see the version logged at the end of the build in one of the last messages (e.g. when building to a folder via the build window)
hey! sorry to just see this now - hard to tell which version I was running when I saw this at first, but it did disappear (seemingly) in Exporter 3.10.3-pre and Engine 3.10.3-beta, as mentioned above. And I’m happy to say that we still haven’t seen it since!
by user 248501710404845568
Thanks. This is not directly tied to the Engine version since the build pipeline version might have automatically updated to the fix (this is a separate npm package) that’s why I’m asking for the console log. But glad to hear it’s working now 