-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Investigate UMD with no global export with webpack #198
Comments
❗ oh no 😿 |
I kno : [ |
Well I guess there's no need to finish the PR? #219 |
@paulfalgout, you're right – there's no reason to finish that Esperanto PR. But this issue is still a valid one. Hopefully #219 fixes it! |
Once #259 lands I should investigate whether webpack makes this any easier |
Gonna close in favor of #264 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At some point my hack for getting around Esperanto's inability to export global variables no longer works. I should:
And
Ref esperantojs/esperanto#96
The text was updated successfully, but these errors were encountered: