-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v7: npm view #1606
v7: npm view #1606
Conversation
edb018c
to
8db5db1
Compare
@@ -0,0 +1,492 @@ | |||
const t = require('tap') | |||
const mr = require('npm-registry-mock') |
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.
just a tip, I have been finding it way simpler to just mock the lib that reaches for the registry in the case of unit tests (in this case pacote
) then setting up a complete registry mock
|
||
dist | ||
.tarball:[36mundefined[39m | ||
.shasum:[33mundefined[39m |
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.
there are quite a few undefined
all over the snapshots, are these expected due to the nature of the mocked data?
[33m6[39m: [object Object] | ||
[33m7[39m: [object Object] | ||
[33m8[39m: [object Object] | ||
[33m9[39m: [object Object] |
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.
were these supposed to be the name?
PR-URL: #1606 Credit: @claudiahdz Close: #1606 Reviewed-by: @isaacs
Landed on 87d27d3. Thanks! |
npm view refactor and unit tests