Skip to content
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(npm): support --allow-scripts on deno run (and deno add, deno test, etc) #26075

Merged
merged 6 commits into from
Oct 12, 2024

Conversation

nathanwhit
Copy link
Member

@nathanwhit nathanwhit commented Oct 9, 2024

Fixes #25533. Fixes #25396.

Previously we only supported it on deno install and deno cache, which is annoying if you're using nodeModulesDir: auto.

Also changes from printing output of lifecycle scripts directly to capturing the output and only printing it on error.

@sigmaSd
Copy link
Contributor

sigmaSd commented Oct 9, 2024

Is it possible for the scripts run with --allow-scripts to follow deno permissions model ? do they currently have allow all permission?

@nathanwhit nathanwhit merged commit 7a990d9 into main Oct 12, 2024
17 checks passed
@nathanwhit nathanwhit deleted the quiet-task-output branch October 12, 2024 19:14
@jerome-benoit
Copy link
Contributor

Is it possible for the scripts run with --allow-scripts to follow deno permissions model ? do they currently have allow all permission?

scripts can be written in shell for examples. Deno does not have any control over the shell interpreter permissions model, if it has one.

@sigmaSd
Copy link
Contributor

sigmaSd commented Oct 14, 2024

@jerome-benoit thanks that clears the confusion I had about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: deno add doesn't support --allow-scripts argument Log more information when a postinstall script fails
4 participants