Merge branch 'main' into feat/example-sveltekit

Author: thisisjofrank

README.md

@@ -65,6 +65,26 @@ deno task reference
 This will generate the reference docs, and you can use the `serve` or `build`
 tasks.
 
+The API reference documentation is generated from type definitions in the
+[Deno source code](https://github.com/denoland/deno). The API reference content
+can be edited by modifying the JSDoc comments in the corresponding `d.ts` files
+in the Deno source code. Once merged, the changes will be reflected in the API
+reference documentation when the Deno documentation site is next updated.
+
+### Previewing API reference changes
+
+In order to preview changes to the API reference, take the following steps:
+
+1. Make changes to the JSDoc comments in the Deno source code
+1. [Build the Deno CLI locally](https://docs.deno.com/runtime/contributing/building_from_source/),
+   including your JSDoc changes
+1. For convenience, create an alias of `d_deno` to point to your local build of
+   the Deno CLI (typically in the `target/debug/deno` directory of your CLI
+   repo)
+1. Generate the reference docs from your local build of the Deno CLI by running
+   in the root directory `d_deno task reference`
+1. Run the `deno task serve` command in the root directory to see the changes
+
 ## Versioning docs content
 
 Philosophically, we want to maintain as few discrete versions of the

_components/Footer.tsx

@@ -88,7 +88,7 @@ const data = [
     items: [
       {
         label: "Blog",
-        href: "https://www.deno.com/blog",
+        href: "https://deno.com/blog",
       },
       {
         label: "Careers",

_components/Header.tsx

@@ -45,7 +45,7 @@ export default function Header({
             url={url}
             activeOn="/runtime"
             href="/runtime/"
-            name="Runtime Manual"
+            name="Manual"
             hideOnMobile
           />
           <HeaderItem

_components/Sidebar.tsx

@@ -22,7 +22,7 @@ export default function Sidebar(
     >
       <ul className="xl:hidden border-bg-tertiary relative bg-background-secondary m-2 mt-0 mb-4 py-2 rounded-md border border-background-tertiary">
         <SidebarTopNav
-          name="Runtime"
+          name="Manual"
           url="/runtime/"
           currentPath={props.url}
         />

copy.client.ts

@@ -1,10 +1,31 @@
-const copyBtns = document.querySelectorAll("button[data-copy]");
-
-copyBtns.forEach((btn) => {
-  btn.addEventListener("click", () => {
-    let textToCopy = btn.getAttribute("data-copy") as string;
-    // CLEAN COMMANDS:  Remove leading spaces, $, and > from each line
-    textToCopy = textToCopy.replace(/^[\$>\s]+/, "");
-    navigator?.clipboard?.writeText(textToCopy);
+document.addEventListener("click", (event) => {
+  const btn = (event.target as HTMLElement).closest("button[data-copy]");
+
+  if (!btn) {
+    return;
+  }
+
+  let textToCopy = btn.getAttribute("data-copy") as string;
+
+  // CLEAN COMMANDS:  Remove leading spaces, $, and > from each line
+  textToCopy = textToCopy.replace(/^[\$>\s]+/, "");
+
+  navigator?.clipboard?.writeText(textToCopy).then(() => {
+    if (!btn) {
+      return;
+    }
+
+    const copyIcon = btn.querySelector(".copy-icon");
+    const checkIcon = btn.querySelector(".check-icon");
+
+    if (copyIcon && checkIcon) {
+      copyIcon.classList.add("hidden");
+      checkIcon.classList.remove("hidden");
+
+      setTimeout(() => {
+        copyIcon.classList.remove("hidden");
+        checkIcon.classList.add("hidden");
+      }, 2000);
+    }
   });
 });

deno.lock

@@ -91,9 +91,9 @@ different compared to other cron engines which use 0-6 representation.
 
 ## Usage on Deno Deploy
 
-With [Deno Deploy](https://www.deno.com/deploy), you can run your background
-tasks on V8 isolates in the cloud. When doing so, there are a few considerations
-to keep in mind.
+With [Deno Deploy](https://deno.com/deploy), you can run your background tasks
+on V8 isolates in the cloud. When doing so, there are a few considerations to
+keep in mind.
 
 ### Differences with Deno CLI
 

deploy/kv/manual/cron.md

@@ -8,7 +8,7 @@ A common use case for [queues](../manual/queue_overview.md) is scheduling work
 to be completed at some point in the future. To help demonstrate how this works,
 we've provided a sample application (described below) that schedules
 notification messages sent through the [Courier API](https://www.courier.com/).
-The application runs on [Deno Deploy](https://www.deno.com/deploy), using the
+The application runs on [Deno Deploy](https://deno.com/deploy), using the
 built-in KV and queue API implementations available there with zero
 configuration.
 

deploy/kv/tutorials/schedule_notification.md

@@ -26,7 +26,7 @@ for **Automatic** and **GitHub Actions** mode.
 ## Automatic
 
 If your project doesn't require any additional build steps, then the system
-choose **Automatic** mode. The entrypoint file is simply the file that Deno
+chooses **Automatic** mode. The entrypoint file is simply the file that Deno
 Deploy will run.
 
 ## GitHub Actions

deploy/manual/ci_github.md

@@ -2,9 +2,9 @@
 title: "Pricing and limitations"
 ---
 
-Please see [our pricing page](https://www.deno.com/deploy/pricing) for the
-overview of the available features in all plans. If you have a use case that
-exceeds any of these limits, [please reach out](mailto:deploy@deno.com).
+Please see [our pricing page](https://deno.com/deploy/pricing) for the overview
+of the available features in all plans. If you have a use case that exceeds any
+of these limits, [please reach out](mailto:deploy@deno.com).
 
 No uptime guarantees are provided during the initial public beta for Deno
 Deploy. Access to the service will be controlled by