Skip to content

Conversation

larsgw
Copy link
Contributor

@larsgw larsgw commented Dec 24, 2018

@larsgw larsgw requested a review from a team as a code owner December 24, 2018 13:04
Copy link
Contributor

@zkat zkat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can use t.match() for better errors btw

@larsgw
Copy link
Contributor Author

larsgw commented Dec 24, 2018

I thought I had seen something like that before, I'll change it in a minute (trying out some tink stuff now).

@zkat zkat added the semver:patch semver patch level for changes label Jan 7, 2019

detail.push(['404', ''])
detail.push(['404', '', "'" + er.pkgid + "' is not in the npm registry."])
detail.push(['404', '', "'" + pkg + "' is not in the npm registry."])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Output should still include the version, because if I say npm i [email protected] I don't want an error saying that npm isn't in the registry.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems I forgot to address this earlier, but I added a fix (not sure why I changed it in the first place).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seeing this makes me want to use template literals. =)

@zkat zkat force-pushed the release-next branch 5 times, most recently from db63b89 to b09bc8c Compare January 23, 2019 18:36
Keep the version number in the error message.

See npm#132 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver:patch semver patch level for changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants