Merge branch 'main' into fix-ui-leave

Author: AugustinMauroy

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+### PR Checklist
+
+- [ ] The PR title follows
+      [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/)
+- [ ] Is this closing an open issue? If so, link it, else include a proper
+      description of the changes and rason behind them.
+- [ ] Does the PR have changes to the frontend? If so, include screenshots or a
+      recording of the changes.
+      <br/>If it affect colors, please include screenshots/recording in both
+      light and dark mode.
+- [ ] Does the PR have changes to the backend? If so, make sure tests are added.
+      <br/>And if changing dababase queries, be sure you have ran `sqlx prepare`
+      and committed the changes in the `.sqlx` directory.

api/.sqlx/query-3dd014058228dbf8302c4944de5c85a1983483c17ca3d6bb7f66cc5c3c88c07e.json renamed to api/.sqlx/query-ce01c6670f8e63d237eedc39bc4e9e1709dc92b0b12e9f7b9e12ba57630faf9a.json

@@ -1385,7 +1385,7 @@ impl Database {
       FROM packages
       LEFT JOIN github_repositories ON packages.github_repository_id = github_repositories.id
       WHERE packages.scope = $1 AND ($2 = true OR packages.is_archived = false)
-      ORDER BY packages.name
+      ORDER BY packages.is_archived ASC, packages.name
       OFFSET $3 LIMIT $4"#,
       scope as _,
       show_archived,

api/src/db/database.rs

@@ -4,6 +4,7 @@ import type { Package, RuntimeCompat } from "../utils/api_types.ts";
 import { getScoreBgColorClass } from "../utils/score_ring_color.ts";
 import type { ListDisplayItem } from "./List.tsx";
 import { RuntimeCompatIndicator } from "./RuntimeCompatIndicator.tsx";
+import TbArchive from "tb-icons/TbArchive";
 
 const runtimeCompatExists = (compat: RuntimeCompat) => {
   return compat?.browser || compat?.deno || compat?.node || compat?.workerd ||
@@ -16,7 +17,7 @@ export function PackageHit(pkg: OramaPackageHit | Package): ListDisplayItem {
     content: (
       <div class="grow-1 w-full flex flex-col md:flex-row gap-2 justify-between">
         <div class="grow-1">
-          <div class="flex flex-wrap items-baseline gap-2">
+          <div class="flex flex-wrap items-baseline gap-x-2 mb-2 md:mb-0">
             <span class="text-jsr-cyan-700 dark:text-cyan-400 font-semibold">
               {`@${pkg.scope}/${pkg.name}`}
             </span>
@@ -25,6 +26,12 @@ export function PackageHit(pkg: OramaPackageHit | Package): ListDisplayItem {
                 {`v${(pkg as Package).latestVersion}`}
               </div>
             )}
+            {(pkg as Package).isArchived && (
+              <div class="text-xs flex items-center gap-1 bg-jsr-yellow-600 text-white px-2 py-0.5 rounded-full">
+                <TbArchive class="size-3" />
+                Archived
+              </div>
+            )}
           </div>
           <div class="text-sm text-tertiary">
             {pkg.description}

deno.lock

@@ -413,7 +413,7 @@ to `jsr publish` or `deno publish`.
 When using Deno, one can supress slow type diagnostics from being surfaced in
 `deno lint` by adding an exclude for the `no-slow-types` rule. This can be done
 by specifying `--rules-exclude=no-slow-types` when running `deno lint`, or by
-adding the following to your `deno.json` configuration file:
+adding the following to your `deno.json(c)` configuration file:
 
 ```json
 {

frontend/components/PackageHit.tsx

@@ -80,7 +80,7 @@ like the name, version, and entrypoint(s). The
 modules should be importable by users of your package.
 
 ```json
-// jsr.json / deno.json
+// jsr.json / deno.json(c)
 {
   "name": "@luca/greet",
   "version": "1.0.0",

frontend/docs/about-slow-types.md

@@ -50,8 +50,8 @@ build for your platform with:
 deno upgrade --canary
 ```
 
-Then, from within your package folder (probably the one with your `deno.json` or
-`mod.ts`), execute the following command:
+Then, from within your package folder (probably the one with your `deno.json(c)`
+or `mod.ts`), execute the following command:
 
 ```bash
 deno run -Ar jsr:@deno/x-to-jsr
@@ -99,7 +99,7 @@ _Vendor dependencies_
 
 You can also
 [vendor your dependencies](https://docs.deno.com/runtime/manual/basics/vendoring/)
-by adding `"vendor": true` to your `deno.json` file. This will download local
+by adding `"vendor": true` to your `deno.json(c)` file. This will download local
 versions of your HTTPS dependencies to a `vendor` directory when the project is
 ran.
 

frontend/docs/introduction.md

@@ -54,7 +54,7 @@ constraints in your code, you can use
 to map the `jsr:` scheme to a different prefix.
 
 In **Deno** you can do this by adding a line to the `"imports"` section in your
-`deno.json`. You can do this manually, or by using the `deno add` command:
+`deno.json(c)`. You can do this manually, or by using the `deno add` command:
 
 ```diff
  {
@@ -64,7 +64,7 @@ In **Deno** you can do this by adding a line to the `"imports"` section in your
  }
 ```
 
-You can then import packages using the alias defined in the `deno.json`:
+You can then import packages using the alias defined in the `deno.json(c)`:
 
 ```ts
 import { camelCase } from "@luca/cases";

frontend/docs/migrate-x-to-jsr.md

@@ -172,7 +172,7 @@ are generated by JSR, and contain all source code reachable from the entrypoint
 of the package. This source code is transpiled to JavaScript, and TypeScript
 type declarations (`.d.ts` files) are generated for all TypeScript files. The
 tarball also contains a `package.json` file that contains the `exports` field
-from the original `jsr.json` / `deno.json` file.
+from the original `jsr.json` / `deno.json(c)` file.
 
 Yanked versions of packages are not advertised in the package version manifest
 of the npm registry endpoint. Tarballs for yanked versions are still available

frontend/docs/native-imports.md

@@ -9,7 +9,7 @@ file can instead be placed in the
 [`deno.json`](https://docs.deno.com/runtime/manual/getting_started/configuration_file).
 
 ```json
-// jsr.json / deno.json
+// jsr.json / deno.json(c)
 {
   "name": "@luca/greet",
   "version": "1.0.0",
@@ -36,7 +36,7 @@ your package. The `exports` field can either be specified as a single string, or
 as an object mapping entrypoint names to paths in your package.
 
 ```json
-// jsr.json / deno.json
+// jsr.json / deno.json(c)
 {
   "name": "@luca/greet",
   "version": "1.0.0",
@@ -58,7 +58,7 @@ you only have a single entrypoint in your package. It is semantically equivalent
 to specifying a default entrypoint in the object form.
 
 ```diff
-// deno.json
+// deno.json(c)
 {
   "name": "@luca/greet",
   "version": "1.0.0",
@@ -72,9 +72,9 @@ to specifying a default entrypoint in the object form.
 ### `include` and `exclude`
 
 You can also use the `include` and `exclude` options to include and exclude
-files during publishing. When using a `deno.json`, you can use `publish.include`
-and `publish.exclude` to include and exclude files only for publishing, rather
-than for all Deno subcommands.
+files during publishing. When using a `deno.json(c)`, you can use
+`publish.include` and `publish.exclude` to include and exclude files only for
+publishing, rather than for all Deno subcommands.
 [Learn more about filtering files](/docs/publishing-packages#filtering-files).
 
 ## JSON Schema