Meteor serves different bundles on same docker image

Hey,
I have been searching for hours but I simply cannot figure out what is happening.

I have 2 servers, both run the identical Docker image. But on one Server a file called gdpr.js found in the browser source tab contains an import that is not in the actual file of the web.browser and web.browser legacy bundles. I have checked both.

n.link("meteor/react-meteor-data", {
    withTracker(e) {
        d = e
    }
}, 4),
n.link("../../../../api/gdpr/gdpr", {
    default(e) {
        p = e
    }
}, 5),

The broken file:

The correct file on the other server:

This import should not be there and it causes an error to be thrown and the application won’t start. I have tried to even recreate the Meteor settings file I pass as an env variable.
But the file still looks the same.
What does Meteor do with built js files? Does it transform them?
When I open the webapp in the same browserm one gets the isModern flag set to true in the runtime config, the other one does not.

what meteor version your project uses?

I am running on Meteor 3.0.2. The application works perfectly fine locally and on the test server.

I also disabled caching, but I have never before opened the page on this server. So Meteor has to transform these files.

I just noticed that the api folder is missing in the screenshot. That is also the issue. The files are simply not loaded on the prod server and it fails with:

Ok i think they are not loaded, because they wouldn’t actually be needed as in the original files these imports are not there.

I fixed the issue, but I am not really sure how this could happen.
We were still using the typescript compiler separately from Meteor, from the time, when there was no real typescript support in Meteor. Replacing it with the meteor typescript package fixes the issue.

But why one server was working and the other one was not, with the exact same Docker image I cannot say…