Using Browserify and RequireJS on the same page?

So i’ve come across an interesting use case where i’m using Browserify to bundle all of my assets together in a project, but a large external (external to the project) module needs to be loaded in when a certain in-app window is accessed. (It’s a video player module made up of three scripts that get pulled in asynchronously when required).

At the moment i’m getting all kinds of errors from uncalled object errors if the requireJS module is loaded in before the Browserified app.js file, to cannot find module errors if loaded in after the Browserified code.

Is there anyway i can get Browserify and RequireJS to play nicely on the same page? I’m losing my mind!

[Pupix]

We had a similar problem, using the --standalone option. If a user was using requirejs, our module would never reach the window, thus making a few web components that needed to access the library through window unusable.

Our fix was to remove the AMD module check and let browserify assign the variable to window. https://github.com/expandjs/expandjs/commit/32765905ea2cb0815f115867e11db192856541e5

[curran]

You can avoid the conflict by changing your AMD code to use the requirejs global rather than the require global, and only have the Browserified code use require. This solution worked for me for having AMD modules and Browserified modules on the same page.