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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@inversifyjs/plugin-dispose

v0.4.0

Published

InversifyJs dispose plugin package

Downloads

249

Readme

Test coverage npm version

@inversifyjs/plugin-dispose

InversifyJS plugin to enable proper disposal of singleton-scoped services when a container is no longer needed.

Installation

npm install @inversifyjs/plugin-dispose inversify

Usage

Registering the Plugin

To use the plugin, you need to register it with your InversifyJS container. The plugin adds support for the standard JavaScript Symbol.dispose and Symbol.asyncDispose interfaces to your container:

import { Container } from 'inversify';
import { PluginDispose } from '@inversifyjs/plugin-dispose';

const container = new Container();

// Register the PluginDispose plugin
container.register(PluginDispose);

Disposing Singleton Services

Once registered, the plugin automatically tracks all singleton-scoped bindings in your container. When it's time to clean up resources, you can use either the synchronous or asynchronous disposal methods:

Synchronous Disposal

// Synchronous disposal
container[Symbol.dispose]();

This will call any registered deactivation handlers for singleton-scoped services in the correct order, ensuring proper cleanup. All deactivation handlers must be synchronous when using this method.

Asynchronous Disposal

// Asynchronous disposal
await container[Symbol.asyncDispose]();

This allows for asynchronous cleanup operations and will properly await all asynchronous deactivation handlers. You can also use the TypeScript using or await using statements for automatic disposal:

// Using 'using' statement for automatic disposal
using container = new Container();
container.register(PluginDispose);
// Container will be disposed when exiting scope

// Using 'await using' for asynchronous disposal
await using asyncContainer = new Container();
asyncContainer.register(PluginDispose);
// Container will be asynchronously disposed when exiting scope

Defining Deactivation Handlers

There are two ways to define deactivation handlers for your services:

Using the onDeactivation Method

interface Database {
  connect(): void;
  disconnect(): Promise<void>;
}

class PostgresDatabase implements Database {
  // Implementation...

  async disconnect(): Promise<void> {
    // Cleanup logic
    console.log('Disconnecting from database');
  }
}

// Register with deactivation handler
container
  .bind<Database>('Database')
  .to(PostgresDatabase)
  .inSingletonScope()
  .onDeactivation(async (instance) => {
    await instance.disconnect();
  });

Using the @preDestroy Decorator

import { preDestroy, injectable } from 'inversify';

@injectable()
class LogService {
  private fileHandle: any;

  constructor() {
    this.fileHandle = { /* some resource */ };
  }

  @preDestroy()
  async cleanup(): Promise<void> {
    // Close file handles, etc.
    console.log('Cleaning up log service');
    this.fileHandle = null;
  }
}

container.bind(LogService).toSelf().inSingletonScope();

How It Works

This plugin automatically:

  1. Tracks all singleton-scoped bindings in your container
  2. Manages the dependency graph to ensure services are disposed in the correct order
  3. Provides standard disposal interfaces (Symbol.dispose and Symbol.asyncDispose)
  4. Invokes any registered deactivation handlers when disposal is triggered

Example

Here's a complete example showing how to use the plugin with services that need proper cleanup:

import { Container, injectable, preDestroy } from 'inversify';
import { PluginDispose } from '@inversifyjs/plugin-dispose';

@injectable()
class DatabaseConnection {
  private isConnected = false;

  constructor() {
    this.connect();
  }

  private connect(): void {
    console.log('Connecting to database');
    this.isConnected = true;
  }

  @preDestroy()
  disconnect(): void {
    if (this.isConnected) {
      console.log('Disconnecting from database');
      this.isConnected = false;
    }
  }
}

@injectable()
class UserRepository {
  constructor(private dbConnection: DatabaseConnection) {}
  
  @preDestroy()
  cleanup(): void {
    console.log('Cleaning up user repository');
  }
}

function buildContainer(): Container {
  // Create and configure container
  const container = new Container();
  container.register(PluginDispose);

  return container;
}

await using container = buildContainer()

// Register services
container.bind(DatabaseConnection).toSelf().inSingletonScope();
container.bind(UserRepository).toSelf().inSingletonScope();

// Use the services
const userRepo = container.get(UserRepository);

// Output:
// Cleaning up user repository
// Disconnecting from database