jeffijoe/awilix

e the scope. If a registration is resolved from a scope that has a cached version of the registration, it will be returned. This is useful for things like request-scoped singletons - i.e. a database transaction, a request cache, a request-specific logger, etc. Scopes are created from a container, and have the same API as the container. **Important:** Scopes are containers too, and can therefore create their own scopes! **Important:** If you use `loadModules` on a scope, it will also load modules from the parent container, but the lifetime of those modules will be determined by the container they were loaded from. ```js const scopedContainer = container.createScope() scopedContainer.cradle.userService.getUser(123) ``` **Important:** if a singleton is resolved, and it depends on a scoped or transient registration, those will remain in the singleton for its lifetime! Similarly, if a scoped module is resolved, and it depends on a transient registration, that remains in the scoped module for its lifetime. In the example above, if `messageService` was a singleton, it would be cached in the root container, and would always have the `currentUser` from the first request. Modules should generally not have a