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.

Sign up for GitHub

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

Jump to bottom

Figure out no-conflict require.js usage #9

Closed
ianb opened this issue Jan 30, 2013 · 1 comment
Closed

Figure out no-conflict require.js usage #9

ianb opened this issue Jan 30, 2013 · 1 comment

Comments

@ianb
Copy link
Contributor

ianb commented Jan 30, 2013

I think we may need to namespace require.js to avoid conflicts with require.js-using applications. This already is an issue with FriendlyCode/Thimble. You can't have multiple baseUrls, which means our baseUrl conflicts with FriendlyCode's.

There are require.js build processes that can namespace require()/etc, but I think we want this even in development.
@ianb ianb mentioned this issue Jan 30, 2013
Closed
@ianb
Copy link
Contributor Author

ianb commented Feb 5, 2013

I think the use of context with require now fixes this.

@ianb ianb closed this as completed Feb 5, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ianb