That’s right, exports is node-specific JS (used to make part of your module available outside the module) and isn’t supported by web-browsers. Even though NodeJS is technically JS, there are client specific properties (like the window property for browsers, and exports for NodeJS apps) that can’t be interchanged. That said, here’s a client side JS … Read more
I have been trying to mix requirejs+Angular for some time now. I published a little project in Github (angular-require-lazy) with my effort so far, since the scope is too large for inline code or fiddles. The project demonstrates the following points: AngularJS modules are lazy loaded. Directives can be lazy loaded too. There is a … Read more
A combination of the 2 answers given here worked for me. //errorInfoHandler.d.ts declare module “lib/errorInfoHandler” { var noTypeInfoYet: any; // any var name here really export = noTypeInfoYet; } I’m still new to TypeScript but it looks as if this is just a way to tell TypeScript to leave off by exporting a dummy variable … Read more
jQuery 1.7 supports AMD loading. But, the trick is avoiding a module naming conflict, since jQuery hardcodes its own module name as ‘jquery’. If you are defining another module as ‘jquery’ (say, in the ‘paths’ property in your requirejs config), it will cause said conflict. To load jQuery in your requirejs application scope, define a … Read more
You’re trying to use a CommonJS module from within your browser. This will not work. How are you using them? When you write import … from … in ES6 Babel will transpile these calls to a module definition called CommonJS and since CommonJS isn’t around in the browser you’ll get an undefined error from require(). … Read more
If you don’t feel like adding a dependency on noext, you can also just append a dummy query string to the path to prevent the .js extension from being appended, as in: require.config({ paths: { ‘signalr-hubs’: ‘/signalr/hubs?noext’ } }); This is what the noext plugin does.
Require.JS is for loading AMD modules. Node.js modules are either ECMAScript modules (which use import and export) or CommonJS modules (which use require and module.exports). Even though both AMD and CommonJS modules use a function named require they are, in general, not compatible. (It is possible to write a module so that it meets the … Read more
FOR TYPESCRIPT 1.7+ It looks like standard is changing again, where the below 0.9+ method still works, but with ES6 coming the following module loading could be used. (reference: https://github.com/TypeStrong/atom-typescript/issues/237#issuecomment-90372105) import * as $ from “jquery”; and even partial ones import {extend} from “jquery”; (this still require the jquery.d.ts, if tsd is installed – tsd … Read more
EDIT (2012-01-30): I pushed a more complete example in a repo on bitbucket. I have successfully used RequireJS to load Ember.js as well as the datetime addon (github). The Ember namespace itself stays global, but all of my application’s data, including my instance of Ember.Application, is kept within modules through RequireJS. I’m also loading the … Read more
With define you register a module in require.js that you can then depend on in other module definitions or require statements. With require you “just” load/use a module or javascript file that can be loaded by require.js. For examples have a look at the documentation My rule of thumb: Define: If you want to declare … Read more