I'm trying to make an external library using Require.js. Thanks to Require.js not compiling single js file correctly and Require.js (almond.js) Timing Off I've figured out how to get everything to "compile" in to a single optimized/built file, and that single file works. There's just one problem: I can't figure out how to set a variable for my library.
Let's say I want my library to create window.Foo
. I tried using a main.js
file with:
window.Foo = require([], function() {
window.Foo = {someValue: 1};
return {someValue: 2};
});
and a wrapper end fragment of:
return require('main');
}));
As you can see, I tried to expose Foo to the global space both by explicitly setting window.Foo
from inside the require call, and setting it explicitly from outside via the return value of the end fragment. But neither one works; if I add a console.log(window.foo)
right after I load the built file, it tells me that window.Foo
is undefined.
If I do a window.setTimeout window.Foo
eventually does get set (to {someValue: 1}
), but I can't very well expect my users to have to wrap all their code with a timeout. Can anyone please explain how I can get window.Foo
to be defined as soon as my optimized/built file is loaded?
Use named exports to export multiple variables in JavaScript, e.g. export const A = 'a' and export const B = 'b' . The exported variables can be imported by using a named import as import {A, B} from './another-file. js' .
Global Variables are the variables that can be accessed from anywhere in the program. These are the variables that are declared in the main body of the source code and outside all the functions. These variables are available to every function to access. Var keyword is used to declare variables globally.
require() statement basically reads a JavaScript file, executes it, and then proceeds to return the export object. require() statement not only allows to add built-in core NodeJS modules but also community-based and local modules.
In JavaScript, variables can be accessed from another file using the <script> tags or the import or export statement. The script tag is mainly used when we want to access variable of a JavaScript file in an HTML file. This works well for client-side scripting as well as for server-side scripting.
If you follow James' instructions here, you can easily produce a library designed as a bundle of RequireJS modules that someone can load synchronously.
I've got a github repository illustrating the whole thing. The salient points:
The main
module exports Foo
to the global space:
define('main', ["./modC"], function () {
console.log("inside");
window.Foo = {someValue: 1};
return {someValue: 2};
});
It also returns a value that is exported by the start fragment as Bar
(that's the line that says root.Bar = factory();
). So it illustrates two ways to export to the global space.
The wrapper code used by r.js
starts main with the synchronous form of require
:
require(`main`);
If you load it, you'll see the following output:
outside
loaded modC
inside
out in the HTML!
value of window.Foo: Object {someValue: 1}
value of window.Bar: Object {someValue: 2}
Calls to require()
are async, meaning the return value of the function that you pass as argument is not returned by require()
itself. Your issue could be solved in different ways, the RequireJS way is defining your code in a module and requiring it as a dependency:
// mymodule.js
define([], function() {
window.Foo = {someValue: 1};
return {someValue: 2};
});
// main.js
require(['mymodule'], function (mymodule) {
console.log(window.Foo); // {someValue: 1}
console.log(mymodule); // {someValue: 2}
});
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With