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
FUTURE: deno install
changes
#23498
FUTURE: deno install
changes
#23498
Conversation
deno install
changesdeno install
changes [WIP]
c707dc3
to
a16ea92
Compare
deno install
changes [WIP]deno install
changes
016861f
to
b6c8d6a
Compare
b6c8d6a
to
b8e7dec
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.
Looks good. Almost there.
cli/args/flags.rs
Outdated
|
||
flags.subcommand = DenoSubcommand::Install(InstallFlags { | ||
// TODO(bartlomieju): remove once `deno install` supports both local and | ||
// global installs |
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.
Is this todo still relevant?
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 think it still applies, but the message is wrong - we want to keep the field for now so we can warn about the behavior change if the user doesn't pass --global
. Updated to reflect 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.
LGTM!
This PR implements the changes we plan to make to
deno install
in deno 2.0.deno install
without arguments caches dependencies frompackage.json
/deno.json
and sets up thenode_modules
folderdeno install <pkg>
adds the package to the config file (eitherpackage.json
ordeno.json
), i.e. it aliasesdeno add
deno add
can also add deps topackage.json
(this is gated behindDENO_FUTURE
due to uncertainty around handling projects with bothdeno.json
andpackage.json
)deno install -g <bin>
installs a package as a globally available binary (the same asdeno install <bin>
in 1.0)