Closed litzebauer closed 7 years ago
A short term workaround is
npm run tagVersion -- --yolo
This skips running the tests before publishing.
In order to conform to np
we can switch the test
script to default to a single tests and have an option to run all tests via npm test all
.
ok, sounds good
On Mon, Feb 27, 2017 at 1:25 PM Matt Fehskens notifications@github.com wrote:
In order to conform to np we can switch the test script to default to a single tests and have an option to run all tests via npm test all.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/gonzofish/angular-library-set/issues/20#issuecomment-282805733, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLc6wYHB6z9L6p468I8iDjisJ6ZgO-Jks5rgxUwgaJpZM4MNUsV .
Verified working on a local test project
When trying to tag a version, "np" runs "npm test" to execute the tests. In angular-library-set "npm test" runs the tests and then stays open watching for changes. This prevents NP from moving beyond the test phase. @gonzofish Not sure how you want to handle this.