New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't define AMD module with a name to make it more portable #62
Comments
Use an anonymous module to make it more portable see jaysalvat#62 based on https://github.com/umdjs/umd/blob/master/returnExports.js `define` and `module` being used as a global add consistency by not using `context.define`.
@arryon I think you can close this issue. |
Done :) |
How should I use it with require.js? |
@norn have you configure your path correctly ? Show us some code. |
@stephanebachelier here it is |
@norn why have you commented the line 'buzz':'//jaysalvat.github.io/buzz/releases/latest/buzz.min'` ? |
I have tried to use the local one on the server and commented the path. But non of them are worked. |
The current AMD module implementation explicitly defines a name for the buzz module, which makes it less portable, see http://requirejs.org/docs/api.html#modulename. If name definition is omitted, this makes the module easier to import into RequireJS.
Can create a pull request if necessary.
The text was updated successfully, but these errors were encountered: