Skip to content
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

Set AMD global before module definition #1590

Merged
merged 1 commit into from
Apr 4, 2014

Conversation

ichernev
Copy link
Contributor

@ichernev ichernev commented Apr 4, 2014

Make sure non AMD compatible modules work well with moment in require.js. This is based on #1574

icambron added a commit that referenced this pull request Apr 4, 2014
Set AMD global before module definition
@icambron icambron merged commit 546fc09 into moment:develop Apr 4, 2014
@icambron
Copy link
Member

icambron commented Apr 4, 2014

Sigh. This kind of thing is everything I hate about JS. That they didn't build modules into the fucking language is infuriating.

@philfreo
Copy link

philfreo commented Apr 4, 2014

Yup, was very frustrating to debug. This change isn't strictly required since wrapShim handles it. You might want to change the wrapShim mention in the docs to say that it's only necessary in X versions since it won't be necessary if this PR is merged.

@ichernev
Copy link
Contributor Author

ichernev commented Apr 4, 2014

The doc states the version exactly. Modules are also pretty hard to get right, you have to agree. The fact that there are multiple semi compatible options is revealing. Languages nowadays ship with package managers... 10 years ago - not so much. Es6 has them. So in 10 years we'll be all set :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants