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

fix #50: browserify -s #103

Merged
merged 1 commit into from
Oct 25, 2014
Merged

fix #50: browserify -s #103

merged 1 commit into from
Oct 25, 2014

Conversation

bollwyvl
Copy link
Contributor

This apparently fixes #50 by using browserify index.js -s dagreD3 instead of browserify browser.js. Looks like the tests pass!

Since the IPython notebook was mentioned, and is what I wanted it for, I've made a notebook with an embedded build.

I don't know how to add testing require.js behavior to the test suite... there is some old doc about using r.js with karma, but I have never worked with it before. It could be that we can just trust browserify, which is usually smarter than me, but I would kind of like to know that this was being looked after.

There are some warnings on the browsersify doc related to how this might affect downstream builds that are explicitly looking for require... I also don't know how to test that until it breaks someone's stuff.

Hopefully this helps!

@cpettitt cpettitt merged commit f425c27 into dagrejs:master Oct 25, 2014
@cpettitt
Copy link
Collaborator

Cool. I agree - tests for the requirejs path would be helpful to ensure this remains stable. Thanks for the patch!

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.

Work with require.js in browser
2 participants