-
Notifications
You must be signed in to change notification settings - Fork 574
Evaluate and rimraf... take two! #110
Evaluate and rimraf... take two! #110
Conversation
package.json
Outdated
"build": "rm -rf dist; tsc -d", | ||
"prepublish": "npm run build; npm test", | ||
"build": "rimraf dist; tsc -d", | ||
"prepublishOnly": "npm run build; npm test", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While we're at it.. does it make sense to switch the order of these two? E.g. Why bother building if the tests don't pass.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. What do you think about using something like np
for release orchestration?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm down with np
!
src/util.ts
Outdated
throw new Error( | ||
result.exceptionDetails.exception.value || | ||
result.exceptionDetails.exception.description | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heads-up: I think we're following the "no-semi" rule
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Odd that my editor didn't catch it. I'll update that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Sorry about that folks, bad rebase and merges. Got too far down the rabbit hole so it was just easier to start fresh :)