Requiring modules CommonJS style in the browser #274
Comments
|
Where is |
|
That's the thing... I don't think it is. Browserify works as an IIFE, so Browserify's require() never exists as a true JavaScript function. Up to now, I'm just having Browserify require() everything I need, and storing those modules in global variables for easy access by my GopherJS code. It works, but it's not ideal, as it necessitates a JavaScript "wrapper" around my GopherJS code. |
|
This may not be the solution you're looking for, but I just want to check you're aware it exists. If you place JavaScript files in the same folder with See #111 for full details. Did you already know about that? |
|
I did not know about that! Is it in the documentation somewhere that I missed? I'm not sure if that will be enough for me, as the order in which some of my JS modules are loaded is important, and my reading of the source code suggests the files are included in a non-deterministic manner (is that accurate?) |
|
The problem here is that the output is |
|
Yes, using |
Is there any way to require external JavaScript modules (CommonJS style) in the browser?
I tried the suggestion in #146:
And that worked fine in nodejs, but it does not work with Browserify (it says
$global.require is not a function). As I understand Browserify, this makes sense, since 'require' isn't a true JS function, but is interpreted by Browserify during its 'compilation'.So is there some other way to make this work, either with Browserify, or with some other third-party Javascript "wrapper"? I'd ideally like one that builds a single output file, so I don't have to worry about providing multiple JS modules via HTTP to the browser, and the complications that come with that.
Or maybe I should request a js.Require() feature be added to gopherjs/js? Is that even practical, given the different use cases anyway? (Presumably it would need to just wrap js.Global.Call("require") for node, but do something more Browserify-ish like slurping in the source JS code when the target is the browser... but AFAIK, GopherJS has no way of knowing, at the moment anyway, whether it's building for the browser or for node)
The text was updated successfully, but these errors were encountered: