node options flag not recognized using gulp and browserify

Browserify shims the core http module with stream-http for browser compatibility, and has a --node flag to prevent this from happening. However, I am unable to do this through gulp, or the documentation does not explain how. I would like to perform the following and not have the stream-http module included in my final browserify bundle:

gulp.task('scripts:server', () => {

    const bundler = browserify(
        'build/source/server.js',
        { 
            debug: true,
            node: true,
        }
    );

    const bundlerError = (err) => {
        console.error(err);
    };

    return bundler.bundle()
        .on('error', bundlerError)
        .pipe(source('server.js'))
        .pipe(buffer())
        .pipe(gulp.dest('dist'));
});

I can see the bare: true and browserField: false do something if I pass them into browserify as options, however, node: true seems to have no effect.

If I run browserify as a command and not through gulp, it works just fine:

browserify --node build/source/server.js -o dist/server.js

[tlopo]

Through the api the parameters necessary to replicate --node are:

        {
            browserField : false,
            builtins : false,
            commondir : false,
            insertGlobalVars : {
                process: undefined,
                global: undefined,
                'Buffer.isBuffer': undefined,
                Buffer: undefined 
            }
        }

That’s how my gulp task looks like:

    gulp.task('default', function() {
        return browserify('./index.js',
        {
            browserField : false,
            builtins : false,
            commondir : false,
            insertGlobalVars : {
                process: undefined,
                global: undefined,
                'Buffer.isBuffer': undefined,
                Buffer: undefined 
            }
        }
    )
        .bundle()
        .pipe(source('bundle.js'))
        .pipe(gulp.dest('./'));
    });

Hope this helps someone.

[tanguy2m]

I faced the same issue using browserify to bundle my javascript modules in an Electron app. I ended-up with the following options:

  ignoreMissing: true,
  builtins: false,
  commondir: false,
  browserField: false,
  detectGlobals: false