ReferenceError: Can't find variable: require_x

[Electroid]

It appears if an import is tree-shaked to not exist, the require_x() function is still included.

// @bun
// /Users/ashcon/Desktop/code/bun/test2/harness.ts
var {callerSourceOrigin } = import.meta.require("bun:jsc");

// test/parallel/test-arm-math-illegal-instruction.js
require_harness();
Object.getOwnPropertyNames(Math).forEach((functionName) => {
  if (!/[A-Z]/.test(functionName))
    Math[functionName](-0.5);
});

//# debugId=544DF241F070613BBBBBBBBBBBBBBBBB
//# sourceMappingURL=data:application/json;base64,ewogICJ2ZXJzaW9uIjogMywKICAic291cmNlcyI6IFs1NDRERjI0MUYwNzA2MTNCQkJCQkJCQkJCQkJCQkJCQiIsCiAgIm5hbWVzIjogW10KfQ==

[Jarred-Sumner]

is this still happening?

[pcfreak30]

I think mine is similar.

#!/usr/bin/env node
var __commonJS = (cb, mod) => () => (mod || cb((mod = { exports: {} }).exports, mod), mod.exports);
var __require = (id) => {
  return import.meta.require(id);
};


// package.json
var require_package = __commonJS((exports, module) => {

i have a case with loader: require

if i hack and replace that with __require still crashes.

also tried loader: Function("return __require;")()

seems to get stuck on its own generated code?

per @Jarred-Sumner Yes the import.meta.require thing is a bug that needs to be fixed.

This is still a bug since at-least 0.7.x.

[pcfreak30]

Still a bug as of 0.8.1.

Also, if i set package.json type to module, i get TypeError: (intermediate value).require is not a function instead on running the bundled file.

[venkatd]

I'm having the same issue as @pcfreak30 also on 0.8.1

[mathiasrw]

A number of issues are connected to this

• bun build --target node injects incorrect require function #6168
• import.meta.require is not a function error after target: "node" build #5707
• [bundler] Do not include import.meta.require in bundled code when building with target: "node" #5154
• ESM bundling for Node produces code for Bun #4861
• ReferenceError: Can't find variable: require_x #2858

Looks like #6168 (comment) got a workaround while we wait for a solution.

[rupurt]

I also get this in bun v1.0.11 when --target bun but only in a compiled executable. Using bun run ... works fine

[Electroid]

This was fixed in a recent release of Bun.