fixed: some examples

grlt-hub · Nov 13, 2024 · 269f4ae · 269f4ae
1 parent 8423fe2
commit 269f4ae
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/website/src/content/docs/how-to-guides/automatically-resolve-dependencies.mdx b/website/src/content/docs/how-to-guides/automatically-resolve-dependencies.mdx
@@ -30,7 +30,7 @@ The `autoResolveDeps` option provides an easy way to automatically resolve conta
 ### Before
 
 ```ts
-import { compose, createContainer } from 'app-compose';
+import { compose, createContainer } from '@grlt-hub/app-compose';
 
 const userEntity = createContainer({
   id: 'userEntity',
@@ -57,7 +57,7 @@ In this case, all containers must be explicitly listed, which becomes cumbersome
 ### After
 
 ```ts {20}
-import { compose, createContainer } from 'app-compose';
+import { compose, createContainer } from '@grlt-hub/app-compose';
 
 const userEntity = createContainer({
   id: 'userEntity',

diff --git a/website/src/content/docs/how-to-guides/handle-container-failures.mdx b/website/src/content/docs/how-to-guides/handle-container-failures.mdx
@@ -20,7 +20,7 @@ In app-compose, containers may fail to initialize properly due to errors in thei
 You can pass an `onFail` function in the `compose.up` configuration to handle container failures globally. The `onFail` function is called whenever any container transitions to the fail state, providing the container's `id` and the `error`:
 
 ```ts {16}
-import { compose, createContainer } from 'app-compose';
+import { compose, createContainer } from '@grlt-hub/app-compose';
 
 const dependency = createContainer({
   id: 'dependency',