Prevent that "require" is exposed as global function

Why does parcel build create build files that expose a global require function and is there a way to prevent that?

// beginning of js build file
require=function(r,e,n) {...

🤔 Expected Behavior

When parcel is used to build libraries that are loaded on 3rd party websites, it should prevent to expose a global require function, because other scripts on that site could rely on a global require function.

😯 Current Behavior

When loading a JS file, which was built with parcel, it exposes require on the window object.

💁 Possible Solution

Add the possibility to configure, if require gets exposed or not.

🔦 Context

Loaded a JS build on a foreign website which relied on a different global require.

[klipstein]

@devinrhode2 the solution was that the function name require is not used anymore (which is utilized by RequireJS and some other loaders) and instead uses parcelRequire as global.

[devinrhode2]

What was the solution? Does parcel still create it’s own require function?