docs: added troubleshooting component (#4255)

docs/content/development/endpoints/add-middleware.mdx

@@ -3,6 +3,10 @@ description: 'Learn how to add a middleware in Medusa. A middleware is a functio
 addHowToData: true
 ---
 
+import Troubleshooting from '@site/src/components/Troubleshooting'
+import ServiceLifetimeSection from '../../troubleshooting/awilix-resolution-error/_service-lifetime.md'
+import CustomRegistrationSection from '../../troubleshooting/awilix-resolution-error/_custom-registration.md'
+
 # Middlewares
 
 In this document, you’ll learn how to add a middleware to an existing or custom route in Medusa.
@@ -103,7 +107,7 @@ In some cases, you may need to register a resource to use within your commerce a
 
 :::tip
 
-If you want to register a logged-in user and access it in your resources, you can check out [this example guide](./example-logged-in-user.md).
+If you want to register a logged-in user and access it in your resources, you can check out [this example guide](./example-logged-in-user.mdx).
 
 :::
 
@@ -151,7 +155,7 @@ Notice that you have to wrap your usage of the new resource in a try-catch block
 
 ### Note About Services Lifetime
 
-If you want to access new registrations in the dependency container within a service, you must set the lifetime of the service either to `Lifetime.SCOPED` or `Lifetime.TRANSIENT`.  Services that have a `Lifetime.SINGLETON` lifetime can't access new registrations since they're resolved and cached in the root dependency container beforehand. You can learn more in the [Create Services documentation](../services/create-service.md#service-life-time).
+If you want to access new registrations in the dependency container within a service, you must set the lifetime of the service either to `Lifetime.SCOPED` or `Lifetime.TRANSIENT`.  Services that have a `Lifetime.SINGLETON` lifetime can't access new registrations since they're resolved and cached in the root dependency container beforehand. You can learn more in the [Create Services documentation](../services/create-service.mdx#service-life-time).
 
 For custom services, no additional action is required as the default lifetime is `Lifetime.SCOPED`. However, if you extend a core service, you must change the lifetime since the default lifetime for core services is `Lifetime.SINGLETON`.
 
@@ -189,6 +193,23 @@ export default ProductService
 
 ---
 
+## Troubleshooting
+
+<Troubleshooting 
+  sections={[
+    {
+      title: 'AwilixResolutionError: Could Not Resolve X',
+      content: <ServiceLifetimeSection />
+    },
+    {
+      title: 'AwilixResolutionError: Could Not Resolve X (Custom Registration)',
+      content: <CustomRegistrationSection />
+    }
+  ]}
+/>
+
+---
+
 ## See Also
 
 - [Store API reference](/api/store)

docs/content/development/endpoints/create.md

@@ -42,7 +42,7 @@ This exports a function that returns an Express router. The function receives tw
 
 ### Defining Multiple Routes or Middlewares
 
-Instead of returning an Express router in the function, you can return an array of routes and [middlewares](./add-middleware.md).
+Instead of returning an Express router in the function, you can return an array of routes and [middlewares](./add-middleware.mdx).
 
 For example:
 

docs/content/development/endpoints/example-logged-in-user.mdx

@@ -3,13 +3,17 @@ description: 'In this document, you’ll see an example of how you can use middl
 addHowToData: true
 ---
 
+import Troubleshooting from '@site/src/components/Troubleshooting'
+import ServiceLifetimeSection from '../../troubleshooting/awilix-resolution-error/_service-lifetime.md'
+import CustomRegistrationSection from '../../troubleshooting/awilix-resolution-error/_custom-registration.md'
+
 # Example: Access Logged-In User
 
 In this document, you’ll see an example of how you can use middlewares and endpoints to register the logged-in user in the dependency container of your commerce application. You can then access the logged-in user in other resources, such as services.
 
 This guide showcases how to register the logged-in admin user, but you can apply the same steps if you want to register the current customer.
 
-This documentation does not explain the basics of [middlewares](./add-middleware.md) and [endpoints](./create.md). You can refer to their respective guides for more details about each.
+This documentation does not explain the basics of [middlewares](./add-middleware.mdx) and [endpoints](./create.md). You can refer to their respective guides for more details about each.
 
 ## Step 1: Create the Middleware
 
@@ -178,7 +182,7 @@ class ProductService extends MedusaProductService {
 export default ProductService
 ```
 
-You can learn more about the importance of changing the service lifetime in the [Middlewares documentation](./add-middleware.md#note-about-services-lifetime).
+You can learn more about the importance of changing the service lifetime in the [Middlewares documentation](./add-middleware.mdx#note-about-services-lifetime).
 
 ---
 
@@ -197,3 +201,20 @@ npx @medusajs/medusa-cli develop
 ```
 
 If you try accessing the endpoints you added the middleware to, you should see your implementation working as expected.
+
+---
+
+## Troubleshooting
+
+<Troubleshooting 
+  sections={[
+    {
+      title: 'AwilixResolutionError: Could Not Resolve X',
+      content: <ServiceLifetimeSection />
+    },
+    {
+      title: 'AwilixResolutionError: Could Not Resolve X (Custom Registration)',
+      content: <CustomRegistrationSection />
+    }
+  ]}
+/>