TypeError: require.resolve is not a function

I used nexe to wrap my node.js application with the following config in package.json:

"nexe": {
    "input": "/usr/local/bin/nexe",
    "output": "myApp.nexe^$",
    "temp": "temp",
    "runtime": {
        "framework": "node",
        "version": "5.5.0",
        "ignoreFlags": false
 }

The executable was generated but when I run it, it reported the following error:

$ ./myApp.nexe 
nexe.js:25933
var processPath = require.resolve('process/browser.js');
                          ^
TypeError: require.resolve is not a function
    at Object.__dirname.150.combine-source-map (nexe.js:25933:27)
    at s (nexe.js:1:316)
    at nexe.js:1:367
    at Object.<anonymous> (nexe.js:11548:21)
    at Object.__dirname.34../lib/builtins.js (nexe.js:12350:4)
    at s (nexe.js:1:316)
    at nexe.js:1:367
    at Object.__dirname.2../log (nexe.js:140:21)
    at s (nexe.js:1:316)
    at nexe.js:1:367

Google search suggested this error might be due to

1. socket.io was used instead of socket.io-client; or
2. the used browserify doesn’t support “require.resolve” while “require” should be used

My app doesn’t use socket.io. And almost all of the libraries my app depends on use the same version of browserify as nexe uses (^13.0.0), except the bluebird library which uses ^8.1.1. I am not sure if that is related. My app doesn’t have any code using “require.resolve(‘process/browser.js’)”. It seems the error happens in the code generated by nexe. So hope I can get some help here.

[jaredallard]

@Thor19 so you can use global.require in place of require(), but this make it use the native node.js version of require. This means that it won’t use the bundled version, and will instead use the one in node_modules (so that must be shipped as well).

[amilajack]

Should this be closed?