npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@proc7ts/context-modules

v7.0.2

Published

Dynamically loadable IoC context modules

Downloads

20

Readme

IoC Context Modules

Dynamically loadable IoC context modules conforming to @proc7ts/context-values API

NPM Build Status Code Quality Coverage GitHub Project API Documentation

Context module can be used to provide multiple assets for IoC context at once. Unloading the module revokes all assets provided by it.

Usage example:

import { CxModule } from '@proc7ts/context-modules';

// Construct new module.
const myModule = new CxModule('my module', {
  setup(setup) {
    // Provide assets for `Foo` entry.
    setup.provide(cxConstAsset(Foo, 'foo'));
  },
});

// Add the module to context.
const myModuleSupply = cxBuilder.provide(myModule);

// Start using the module.
// The first usage of the module loads it.
const myModuleUse = await context.get(myModule).use();

// Await for the module to load.
await myModuleUse.whenReady;

// Access the value provided by module.
console.log(context.get(Foo)); // 'foo'

// Stop using the module.
// Once tha last usage stopped, the module is unloaded.
myModuleUse.supply.off();

// Revoke the module.
myModuleSupply.off();

Context module's constructor accepts a human-readable module name, and options object.

The following options supported:

  • needs - A module or modules the constructed one requires.

    The listed modules will be loaded prior to loading the constructed one.

  • has - A module or modules the constructed one provides.

    When specified, the constructed module will be loaded instead of the listed ones.

  • setup() - A method that sets up constructed module.

    May be synchronous or asynchronous.

    Accepts a CxModule.Setup instance with the following properties:

    • get() - For accessing context values.

      Inherited from ContextValues interface.

    • provide() - For providing context entry assets.

      The same as in CxBuilder.

      All assets provided by this method will be revoked once the module unloaded.

    • initBy() - For registering module initializers.

To use a module:

  1. Create its implementation.

  2. Provide it by CxBuilder.provide(module) call.

  3. Obtain its handle from context by calling CxValues.get(module).

  4. Start using it by calling the .use() method of obtained module handle.

  5. Wait for the module to load and become ready to use: await use.whenReady.

  6. When no longer needed, cut off the module use supply: use.supply.off().

    The module will be unloaded once no longer uses remain.

    Note that the module can be in use indirectly when required by another one.