We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/umdjs/umd/blob/master/templates/amdWebGlobal.js
What about case when i have amd, but for any architecture reasons i dont use it, but i still want just to include library and get global variable.
More correctly will be:
define(['b'], function (b) { return factory(b); }); root.amdWebGlobal = require('b');
because global variables are for "inline" usages, not for amd approach.
"backward compatibility" of libraries should not be affected by my architecture.
why by adding third party amd it should breaks existing usages of any library?
this is definitely wrong approach.
The text was updated successfully, but these errors were encountered:
+1
Sorry, something went wrong.
Example of real problem: DmitryBaranovskiy/raphael#1026 (comment)
No branches or pull requests
https://github.com/umdjs/umd/blob/master/templates/amdWebGlobal.js
What about case when i have amd, but for any architecture reasons i dont use it, but i still want just to include library and get global variable.
More correctly will be:
because global variables are for "inline" usages, not for amd approach.
"backward compatibility" of libraries should not be affected by my architecture.
why by adding third party amd it should breaks existing usages of any library?
this is definitely wrong approach.
The text was updated successfully, but these errors were encountered: