Merge branch 'main' into create-remix-cli-package-managers

contributors.yml

@@ -7,6 +7,7 @@
 - achinchen
 - adamwathan
 - adicuco
+- AdiRishi
 - ahabhgk
 - ahbruns
 - ahmedeldessouki
@@ -646,6 +647,7 @@
 - wilcoschoneveld
 - willhack
 - willin
+- willowcheng
 - wizardlyhel
 - wKovacs64
 - wladiston

docs/guides/errors.md

@@ -81,7 +81,7 @@ export function ErrorBoundary() {
 }
 ```
 
-If you need to log these errors or report then to a third-party service such as [BugSnag][bugsnag] or [Sentry][sentry], then you can do this through a [`handleError`][handle-error] export in your [`app/entry.server.js`][entry-server]. This method receives the un-sanitized versions of the error since it is also running on the server.
+If you need to log these errors or report them to a third-party service such as [BugSnag][bugsnag] or [Sentry][sentry], then you can do this through a [`handleError`][handle-error] export in your [`app/entry.server.js`][entry-server]. This method receives the un-sanitized versions of the error since it is also running on the server.
 
 If you want to trigger an error boundary and display a specific message or data in the browser, then you can throw a `Response` from a `action`/`loader` with that data instead:
 

templates/cloudflare/package.json

@@ -16,12 +16,12 @@
     "@remix-run/cloudflare-pages": "*",
     "@remix-run/react": "*",
     "isbot": "^4.1.0",
-    "miniflare": "^3.20231030.4",
+    "miniflare": "^3.20240404.0",
     "react": "^18.2.0",
     "react-dom": "^18.2.0"
   },
   "devDependencies": {
-    "@cloudflare/workers-types": "^4.20230518.0",
+    "@cloudflare/workers-types": "^4.20240405.0",
     "@remix-run/dev": "*",
     "@types/react": "^18.2.20",
     "@types/react-dom": "^18.2.7",
@@ -37,7 +37,7 @@
     "typescript": "^5.1.6",
     "vite": "^5.1.0",
     "vite-tsconfig-paths": "^4.2.1",
-    "wrangler": "^3.24.0"
+    "wrangler": "^3.48.0"
   },
   "engines": {
     "node": ">=18.0.0"