Fixes test suite for the breaking changes to node packages #11
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
kritzcreek
force-pushed
the
breaking-node-changes
branch
from
7feda0b to
8f0d617
Compare
kritzcreek
force-pushed
the
breaking-node-changes
branch
from
8f0d617 to
6a39f3a
Compare
|
I can open kritzcreek#1 as a follow-up if you think switching to the next iteration of spago is a good idea yet. The main benefit imo is that we could split off the test dependencies from the library ones. |
|
I would be OK with switching to spago@next. |
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.
I also added the npm files to install the compiler, spago and tidy. Happy to delete those if you'd rather not have them around.
(My main motivation was to maybe get this back into the package-set rotation)