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
Follow-up from #15 - if you have a named export, Esperanto will avoid naming collisions at the top level:
// this... import { a } from 'foo'; a(); var foo = 'bar'; // ...becomes this define(['foo'], function (_foo) { 'use strict'; _foo.a(); var foo = 'bar'; });
But it's possible to shadow an import name:
// this... import { a } from 'foo'; a(); (function () { var foo = 'bar'; a(); }()) // ...becomes this, which won't work define(['foo'], function (foo) { 'use strict'; foo.a(); (function () { var foo = 'bar'; foo.a(); }()) });
The text was updated successfully, but these errors were encountered:
test for #18
beacdee
209b117
fixes #18 (shadowed imports) with renamed imports in bundles
e4857af
No branches or pull requests
Follow-up from #15 - if you have a named export, Esperanto will avoid naming collisions at the top level:
But it's possible to shadow an import name:
The text was updated successfully, but these errors were encountered: