core: introduce extensions (#9800)

Extensions allow declarative extensions to "JsRuntime" (ops, state, JS or middleware).

This allows for:
- `op_crates` to be plug-and-play & self-contained, reducing complexity leaked to consumers
- op middleware (like metrics_op) to be opt-in and for new middleware (unstable, tracing,...)
- `MainWorker` and `WebWorker` to be composable, allowing users to extend workers with their ops whilst benefiting from the other infrastructure (inspector, etc...)

In short extensions improve deno's modularity, reducing complexity and leaky abstractions for embedders and the internal codebase.

1 files changed, 0 insertions, 23 deletions

diff --git a/runtime/ops/file.rs b/runtime/ops/file.rs
deleted file mode 100644
index 8f471ebbd..000000000
--- a/runtime/ops/file.rs
+++ /dev/null
@@ -1,23 +0,0 @@
-// Copyright 2018-2021 the Deno authors. All rights reserved. MIT license.
-use deno_core::url::Url;
-use deno_file::op_file_create_object_url;
-use deno_file::op_file_revoke_object_url;
-use deno_file::BlobUrlStore;
-use deno_file::Location;
-
-pub fn init(
-  rt: &mut deno_core::JsRuntime,
-  blob_url_store: BlobUrlStore,
-  maybe_location: Option<Url>,
-) {
-  {
-    let op_state = rt.op_state();
-    let mut op_state = op_state.borrow_mut();
-    op_state.put(blob_url_store);
-    if let Some(location) = maybe_location {
-      op_state.put(Location(location));
-    }
-  }
-  super::reg_sync(rt, "op_file_create_object_url", op_file_create_object_url);
-  super::reg_sync(rt, "op_file_revoke_object_url", op_file_revoke_object_url);
-}