denoland-deno/runtime/permissions/Cargo.toml

# Copyright 2018-2024 the Deno authors. All rights reserved. MIT license.

[package]
name = "deno_permissions"
version = "0.18.0"
authors.workspace = true
edition.workspace = true
license.workspace = true
repository.workspace = true
description = "Provides the deno permissions implementation."

[lib]
name = "deno_permissions"
path = "lib.rs"

[dependencies]
deno_core.workspace = true
deno_terminal.workspace = true
fqdn = "0.3.4"
libc.workspace = true
log.workspace = true
once_cell.workspace = true
serde.workspace = true
which = "4.2.5"

[target.'cfg(windows)'.dependencies]
winapi = { workspace = true, features = ["commapi", "knownfolders", "mswsock", "objbase", "psapi", "shlobj", "tlhelp32", "winbase", "winerror", "winuser", "winsock2", "processenv", "wincon", "wincontypes"] }
refactor: add `deno_permissions` crate (#22236) Issue https://github.com/denoland/deno/issues/22222 ![image](https://github.com/denoland/deno/assets/34997667/2af8474b-b919-4519-98ce-9d29bc7829f2) This PR moves `runtime/permissions` code to a upstream crate called `deno_permissions`. The `deno_permissions::PermissionsContainer` is put into the OpState and can be used instead of the current trait-based permissions system. For this PR, I've migrated `deno_fetch` to the new crate but kept the rest of the trait-based system as a wrapper of `deno_permissions` crate. Doing the migration all at once is error prone and hard to review. Comparing incremental compile times for `ext/fetch` on Mac M1: \| profile \| `cargo build --bin deno` \| `cargo plonk build --bin deno` \| \| --------- \| ------------- \| ------------------- \| \| `debug` \| 20 s \| 0.8s \| \| `release` \| 4 mins 12 s \| 1.4s \| 2024-03-12 10:42:26 -07:00			`# Copyright 2018-2024 the Deno authors. All rights reserved. MIT license.`

			`[package]`
			`name = "deno_permissions"`
chore: forward v1.44.4 release commit to main (#24271) This is the release commit being forwarded back to main for 1.44.4 Co-authored-by: bartlomieju <bartlomieju@users.noreply.github.com> 2024-06-20 03:29:53 +09:00			`version = "0.18.0"`
refactor: add `deno_permissions` crate (#22236) Issue https://github.com/denoland/deno/issues/22222 ![image](https://github.com/denoland/deno/assets/34997667/2af8474b-b919-4519-98ce-9d29bc7829f2) This PR moves `runtime/permissions` code to a upstream crate called `deno_permissions`. The `deno_permissions::PermissionsContainer` is put into the OpState and can be used instead of the current trait-based permissions system. For this PR, I've migrated `deno_fetch` to the new crate but kept the rest of the trait-based system as a wrapper of `deno_permissions` crate. Doing the migration all at once is error prone and hard to review. Comparing incremental compile times for `ext/fetch` on Mac M1: \| profile \| `cargo build --bin deno` \| `cargo plonk build --bin deno` \| \| --------- \| ------------- \| ------------------- \| \| `debug` \| 20 s \| 0.8s \| \| `release` \| 4 mins 12 s \| 1.4s \| 2024-03-12 10:42:26 -07:00			`authors.workspace = true`
			`edition.workspace = true`
			`license.workspace = true`
			`repository.workspace = true`
			`description = "Provides the deno permissions implementation."`

			`[lib]`
			`name = "deno_permissions"`
			`path = "lib.rs"`

			`[dependencies]`
			`deno_core.workspace = true`
			`deno_terminal.workspace = true`
fix(runtime): use FQDN in NetDescriptor (#23084) 2024-03-26 23:27:40 +00:00			`fqdn = "0.3.4"`
refactor: add `deno_permissions` crate (#22236) Issue https://github.com/denoland/deno/issues/22222 ![image](https://github.com/denoland/deno/assets/34997667/2af8474b-b919-4519-98ce-9d29bc7829f2) This PR moves `runtime/permissions` code to a upstream crate called `deno_permissions`. The `deno_permissions::PermissionsContainer` is put into the OpState and can be used instead of the current trait-based permissions system. For this PR, I've migrated `deno_fetch` to the new crate but kept the rest of the trait-based system as a wrapper of `deno_permissions` crate. Doing the migration all at once is error prone and hard to review. Comparing incremental compile times for `ext/fetch` on Mac M1: \| profile \| `cargo build --bin deno` \| `cargo plonk build --bin deno` \| \| --------- \| ------------- \| ------------------- \| \| `debug` \| 20 s \| 0.8s \| \| `release` \| 4 mins 12 s \| 1.4s \| 2024-03-12 10:42:26 -07:00			`libc.workspace = true`
			`log.workspace = true`
			`once_cell.workspace = true`
			`serde.workspace = true`
			`which = "4.2.5"`

			`[target.'cfg(windows)'.dependencies]`
fix(ext/permissions): add correct feature flags to winapi (#24218) 2024-06-17 01:29:16 -04:00			`winapi = { workspace = true, features = ["commapi", "knownfolders", "mswsock", "objbase", "psapi", "shlobj", "tlhelp32", "winbase", "winerror", "winuser", "winsock2", "processenv", "wincon", "wincontypes"] }`