-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
feat: infer dependencies from package.json #22563
Conversation
vec![ | ||
("NPM_CONFIG_REGISTRY".to_string(), npm_registry_url()), | ||
("JSR_URL".to_string(), jsr_registry_url()), | ||
("NO_COLOR".to_string(), "1".to_string()), |
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.
Had to add a new function because we need both the npm env + jsr env.
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.
With the local registry in the tests, we pull tarballs from the folders in tests/testdata/npm/registry/
.
chalk
is already in there, so if you use that instead of camelcase
, you do not need to check in the node_modules/
folder.
0768d49
to
d8c69e1
Compare
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.
LGTM!
This PR enhances the
deno publish
command to infer dependencies frompackage.json
if present.