@dotcom-reliability-kit/middleware-render-error-info - npm Package Compare versions

Comparing version 4.1.0 to 4.1.1

package.json

 {
   "name": "@dotcom-reliability-kit/middleware-render-error-info",
-  "version": "4.1.0",
+  "version": "4.1.1",
   "description": "Express middleware to render error information in a way that makes local debugging easier and production error rendering more consistent.",
@@ -20,4 +20,4 @@ "repository": {
     "@dotcom-reliability-kit/app-info": "^2.3.0",
-    "@dotcom-reliability-kit/log-error": "^3.1.6",
-    "@dotcom-reliability-kit/serialize-error": "^2.2.0",
+    "@dotcom-reliability-kit/log-error": "^3.1.7",
+    "@dotcom-reliability-kit/serialize-error": "^2.2.1",
     "entities": "^4.5.0"
@@ -24,0 +24,0 @@ },

README.md

@@ -34,3 +34,3 @@
 
-> **Warning**
+> [!CAUTION]<br />
 > This middleware **must** be added to your Express app _after_ all your application routes – you won't get rendered errors for any routes which are mounted after this middleware.
@@ -44,3 +44,3 @@
 
-> **Warning**
+> [!CAUTION]<br />
 > If you're using [@dotcom-reliability-kit/middleware-log-errors](https://github.com/Financial-Times/dotcom-reliability-kit/tree/main/packages/middleware-log-errors#readme) in your app, it's best to mount the error page middleware _after_ the logging middleware. Otherwise the error will never be logged.
@@ -47,0 +47,0 @@

No alert changes

Improved metrics

Total package byte prevSize

28410

increased by0.04%

Dependency changes

• Updated@dotcom-reliability-kit/log-error@^3.1.7

• Updated@dotcom-reliability-kit/serialize-error@^2.2.1