Add mithril and mithril-query, rearchitect gopm tool #6
Conversation
This file contains 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
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.
In addition to adding a gopherjs wrapper for mithril (based on Danver Braganza's earlier work) and mithril-query, this PR makes significant changes to the gopherjs workflow for this repo:
Instead of having to manually write a package.json in a "main" package, this new workflow instead inverts the problem and has packages that wrap javascript libraries include their own package.json files to directly declare their dependencies. Packages that depend upon js wrapper packages no longer need to configure anything: the gopm commands will automatically calculate all dependencies and merge them into a single package.json file that can be used to install all node dependencies.