format all the things

Author: kentcdodds

app/utils/honeypot.server.ts

@@ -1,7 +1,7 @@
 import { Honeypot, SpamError } from 'remix-utils/honeypot/server'
 
 export const honeypot = new Honeypot({
-	validFromFieldName: process.env.NODE_ENV === "test" ? null : undefined,
+	validFromFieldName: process.env.NODE_ENV === 'test' ? null : undefined,
 	encryptionSeed: process.env.HONEYPOT_SECRET,
 })
 

docs/authentication.md

@@ -89,8 +89,8 @@ app could have been registered with an Organisation or another person's GitHub
 account.
 
 Also make sure to register separate additional OAuth apps for each of your
-deployed environments (e.g. `staging` and `production`) and specify corresponding
-homepage and redirect urls in there.
+deployed environments (e.g. `staging` and `production`) and specify
+corresponding homepage and redirect urls in there.
 
 ## TOTP and Two-Factor Authentication
 

docs/caching.md

@@ -23,9 +23,9 @@ indexes before caching the results.
 ## Using the cache
 
 You won't typically interact directly with the caches. Instead, you will use
-[`cachified`](https://www.npmjs.com/package/@epic-web/cachified) which is a nice abstraction for cache
-management. We have a small abstraction on top of it which allows you to pass
-`timings` to work seamlessly with
+[`cachified`](https://www.npmjs.com/package/@epic-web/cachified) which is a nice
+abstraction for cache management. We have a small abstraction on top of it which
+allows you to pass `timings` to work seamlessly with
 [the server timing utility](./server-timing.md).
 
 Let's say we're making a request to tito to get a list of events. Tito's API is

docs/decisions/036-vite.md

@@ -23,16 +23,17 @@ vite plugin will fail the build if it finds any issues so if it builds, it
 works. Additionally, this will help us make a cleaner separation between server
 and server/client code which is a good thing.
 
-The simple rule is this: if it's a Remix export (like `loader`, or `action`) then
-it can be in the route. If it's our own utility export (like
-`requireRecentVerification` we had in the `/verify` route) then it needs to go in
-a `.server` file. To be clear, if you don't export it, then it's fine. Server-only
-utility functions are fine in routes. It just becomes a problem for remix when
-they are exported.
-
-An interesting exception to this is sever-only code in the `handle` export like the
-[`getSitemapEntries` function](https://github.com/nasa-gcn/remix-seo). For this,
-you need to use [`vite-env-only`](https://github.com/pcattori/vite-env-only).
+The simple rule is this: if it's a Remix export (like `loader`, or `action`)
+then it can be in the route. If it's our own utility export (like
+`requireRecentVerification` we had in the `/verify` route) then it needs to go
+in a `.server` file. To be clear, if you don't export it, then it's fine.
+Server-only utility functions are fine in routes. It just becomes a problem for
+remix when they are exported.
+
+An interesting exception to this is sever-only code in the `handle` export like
+the [`getSitemapEntries` function](https://github.com/nasa-gcn/remix-seo). For
+this, you need to use
+[`vite-env-only`](https://github.com/pcattori/vite-env-only).
 
 ## Decision
 
@@ -41,5 +42,5 @@ Adopt vite.
 ## Consequences
 
 Almost everything is better. We have slightly more complicated rules around the
-server/client code separation, but for the most part that's better and there are fewer
-surprises.
+server/client code separation, but for the most part that's better and there are
+fewer surprises.

docs/examples.md

@@ -91,10 +91,19 @@ This page links to examples of how to implement some things with the Epic Stack.
 - [Epic Stack Border animation](https://github.com/hakimLyon/epic-stack-with-css-border-animation)
   by [@hakimLyon](https://github.com/hakimLyon): An example of Epic Stack with a
   CSS border animation.
-- [Epic Stack with Keystatic](https://github.com/simonswiss/epic-stack-with-keystatic) by [@simonswiss](https://github.com/simonswiss): An example adding a MDX blog, editable from an elegant Admin UI with Keystatic.
-- [Epic Stack + Ariakit](https://github.com/gnapse/epic-stack) by [@gnapse](https://github.com/gnapse): A fork of the Epic Stack that uses [Ariakit](https://ariakit.org/) instead of Radix UI.
-- [Epic Stack + Stripe Payments](https://github.com/saurabhp75/epic-stripe) by [@saurabhp75](https://github.com/saurabhp75): An example of Epic Stack with [Stripe](https://ariakit.org/) payments.
-- [Epic Stack + Remix PWA](https://github.com/ShafSpecs/offline-epic-stack) by [@ShafSpecs](https://github.com/ShafSpecs): An example of using Epic Stack offline with [Remix PWA](https://remix-pwa.run). The guide can be found [here](https://remix-pwa.run/docs/main/offline)
+- [Epic Stack with Keystatic](https://github.com/simonswiss/epic-stack-with-keystatic)
+  by [@simonswiss](https://github.com/simonswiss): An example adding a MDX blog,
+  editable from an elegant Admin UI with Keystatic.
+- [Epic Stack + Ariakit](https://github.com/gnapse/epic-stack) by
+  [@gnapse](https://github.com/gnapse): A fork of the Epic Stack that uses
+  [Ariakit](https://ariakit.org/) instead of Radix UI.
+- [Epic Stack + Stripe Payments](https://github.com/saurabhp75/epic-stripe) by
+  [@saurabhp75](https://github.com/saurabhp75): An example of Epic Stack with
+  [Stripe](https://ariakit.org/) payments.
+- [Epic Stack + Remix PWA](https://github.com/ShafSpecs/offline-epic-stack) by
+  [@ShafSpecs](https://github.com/ShafSpecs): An example of using Epic Stack
+  offline with [Remix PWA](https://remix-pwa.run). The guide can be found
+  [here](https://remix-pwa.run/docs/main/offline)
 
 ## How to contribute
 

docs/features.md

@@ -22,8 +22,8 @@ Here are a few things you get today:
 - Database ORM with [Prisma](https://prisma.io/)
 - Role-based User Permissions.
 - Custom built image hosting
-- Caching via [cachified](https://npm.im/@epic-web/cachified): Both in-memory and
-  SQLite-based (with
+- Caching via [cachified](https://npm.im/@epic-web/cachified): Both in-memory
+  and SQLite-based (with
   [better-sqlite3](https://github.com/WiseLibs/better-sqlite3))
 - Styling with [Tailwind](https://tailwindcss.com/)
 - An excellent, customizable component library with

docs/fonts.md

@@ -14,9 +14,8 @@ don't) you can generate one using a tool like
 [Transfonter](https://transfonter.org/). Transfonter now has a fonts directory
 setting. Set that to `fonts` to have the `url` preset.
 
-Verify the `url` in the `css` is relative to the `public` 
-folder. So it should look something like
-`url('/fonts/yourfont/yourfont-200.woff2')`.
+Verify the `url` in the `css` is relative to the `public` folder. So it should
+look something like `url('/fonts/yourfont/yourfont-200.woff2')`.
 
 Now you've added your font, there's a few places you need to update to use it.
 

docs/monitoring.md

@@ -39,10 +39,10 @@ To generate the auth token, click
 [this](https://sentry.io/orgredirect/settings/:orgslug/developer-settings/new-internal/)
 to create an internal integration (which grants the selected capabilities to the
 recipient, similar to how RBAC works). Give it a name and add the scope for
-`Releases:Admin` and `Organization:Read`. Press Save, find the auth token at the bottom of the page
-under "Tokens", and copy that to secure location (this becomes
-`SENTRY_AUTH_TOKEN`). Then visit the organization settings page and copy that
-organization slug (`SENTRY_ORG`), and the slug name for your project too
+`Releases:Admin` and `Organization:Read`. Press Save, find the auth token at the
+bottom of the page under "Tokens", and copy that to secure location (this
+becomes `SENTRY_AUTH_TOKEN`). Then visit the organization settings page and copy
+that organization slug (`SENTRY_ORG`), and the slug name for your project too
 (`SENTRY_PROJECT`).
 
 In the 'build' section of the [Dockerfile](../other/Dockerfile), there is an

tests/mocks/index.ts

@@ -6,18 +6,18 @@ import { handlers as resendHandlers } from './resend.ts'
 export const server = setupServer(...resendHandlers, ...githubHandlers)
 
 server.listen({
-  onUnhandledRequest(request, print) {
-    // Do not print warnings on unhandled requests to https://<:userId>.ingest.us.sentry.io/api/
-    // Note: a request handler with passthrough is not suited with this type of url
-    //       until there is a more permissible url catching system
-    //       like requested at https://github.com/mswjs/msw/issues/1804
-    if (request.url.includes('.sentry.io')) {
-      return
-    }
+	onUnhandledRequest(request, print) {
+		// Do not print warnings on unhandled requests to https://<:userId>.ingest.us.sentry.io/api/
+		// Note: a request handler with passthrough is not suited with this type of url
+		//       until there is a more permissible url catching system
+		//       like requested at https://github.com/mswjs/msw/issues/1804
+		if (request.url.includes('.sentry.io')) {
+			return
+		}
 
-    // Print the regular MSW unhandled request warning otherwise.
-    print.warning()
-  }
+		// Print the regular MSW unhandled request warning otherwise.
+		print.warning()
+	},
 })
 
 if (process.env.NODE_ENV !== 'test') {

tsconfig.json

@@ -17,11 +17,11 @@
       "#*": ["./*"],
       "@/icon-name": [
         "./app/components/ui/icons/name.d.ts",
-        "./types/icon-name.d.ts",
-      ],
+        "./types/icon-name.d.ts"
+      ]
     },
     "skipLibCheck": true,
     "allowImportingTsExtensions": true,
-    "noEmit": true,
-  },
+    "noEmit": true
+  }
 }