Open
Conversation
while keeping client-side usage unchanged using UMD (Universal Module Definition) returnExports pattern https://github.com/umdjs/umd
apparently, github doesn't parse titles without space after the pound key anymore.
avoid hard-coded http scheme so that d3 doesn't get blocked as mixed active content
|
@upphiminn Any update on this? |
|
Nevermind that - https://github.com/jgranstrom/jLouvain |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
made compatible with node.js #4 😄 using UMD (Universal Module Definition) returnExports pattern
A further enhancement could be to publish the module in npm, may be done separately from this pull request.