-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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: Handle package.json lifecycle scripts #23558
Conversation
@@ -648,6 +737,39 @@ fn get_package_folder_id_from_folder_name( | |||
}) | |||
} | |||
|
|||
fn symlink_bin_entry( |
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.
We have some code somewhere else that handles doing a symlink like this on unix and will use junctions on windows. It would be good to reuse that code here.
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.
Or actually, I guess since this is setting up scripts for windows we should have it create something executable here for that.
cli/npm/managed/resolvers/local.rs
Outdated
log::warn!(" Do you want to run this script with full permissions? [y/N]"); | ||
// ASCII code for the bell character. | ||
print!("\x07"); | ||
eprint!(" > "); |
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.
Could a previously executing script stuff stdin? We should maybe re-use the permission prompt code here somehow?
Closing in favor of #24487 |
Blocked by #23498Blocked by #23496Blocked by denoland/deno_npm#47Blocked by denoland/eszip#182