Added recursive-ci next to recursive-install. #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
Updated npm install to npm ci.
Supporting production parameter. Resolving tests: - no longer rely on node being the application associated with .js files on Windows. - added a test for an invalid package-lock.json file. Upgraded dependencies and devDependencies to the latest versions.
Restructured tests to accommodate tests for recursive-install as well as recursive-ci.js Added tools.js to re-use code between recursive-install and recursive-ci.
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.
Since the functionality is very similar and at least a section of the code can be re-used (cfr. lib/tools.js) between both, I think it would make sense to store everything in a single git repository rather than maintaining multiple forks.
Changes: