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 🙏

© 2025 – Pkg Stats / Ryan Hefner

critical-section

v0.2.0

Published

A mutual exclusion library using objects as lock identifiers

Readme

Critical Section

CI npm

A lightweight TypeScript/JavaScript library for object-based mutual exclusion that treats your domain objects as natural lock identifiers.

Why Critical Section?

Turn any object into a critical section lock - no string keys, no separate mutex instances to manage:

// Use your existing objects directly as locks
const user = { id: 123, name: 'John' };
await criticalSection.enter(user);

// Global objects work perfectly too
await criticalSection.enter(document);
await criticalSection.enter(window);

Key Features

  • 🎯 Object-centric design: Your domain objects become the locks themselves
  • 🧠 Intuitive mental model: One object = one critical section, naturally aligned with OOP
  • ♻️ Automatic cleanup: WeakMap prevents memory leaks through garbage collection
  • ⚡ Lightweight: Just 5 methods - enter(), tryEnter(), waitLeave(), isLocked(), leave()
  • 🌐 Universal: Works in Node.js, browsers, and all modern JavaScript environments
  • 🔒 Type-safe: Full TypeScript support with strict type checking
  • 📦 Zero dependencies: No external runtime dependencies

Installation

npm install critical-section

Quick Start

import { criticalSection } from 'critical-section';

// Any object becomes a critical section lock
const database = { host: 'localhost', db: 'users' };
const userRecord = { id: 123, email: '[email protected]' };

async function updateUser() {
  // Lock the specific user record to prevent race conditions
  const entered = await criticalSection.enter(userRecord);

  if (entered) {
    try {
      console.log('Updating user record...');
      await validateUserData(userRecord);
      await performDatabaseUpdate(userRecord);
      await updateSearchIndex(userRecord);
      // All 3 operations complete atomically - no partial updates
    } finally {
      // Always release the lock
      criticalSection.leave(userRecord);
    }
  }
}

// Try immediate access without waiting
async function quickUserCheck() {
  if (criticalSection.tryEnter(userRecord)) {
    try {
      console.log('Quick read operation');
      const userData = await readUserData(userRecord);
      return userData;
    } finally {
      criticalSection.leave(userRecord);
    }
  } else {
    console.log('User record is busy, using cache...');
    return await getCachedUserData(userRecord.id);
  }
}

// Multiple objects = independent locks
await Promise.all([
  updateUser(),           // Uses userRecord lock
  cleanupDatabase(),      // Uses database lock - runs concurrently!
]);

API

criticalSection.enter(obj: object, timeout?: number): Promise<boolean>

Enters a critical section for the given object. If the critical section is already occupied, the promise will wait until it becomes available or times out.

Parameters:

  • obj - Any object to use as the critical section identifier
  • timeout (optional) - Maximum time to wait in milliseconds. If not provided, waits indefinitely

Returns:

  • Promise<boolean> - Resolves to true when successfully entered, false if timeout occurs

Examples:

// Wait indefinitely
const success = await criticalSection.enter(myResource);
if (success) {
  // Critical section is now entered
}

// Wait with timeout
const entered = await criticalSection.enter(myResource, 5000);
if (entered) {
  // Got access within 5 seconds
} else {
  // Timeout occurred
}

criticalSection.tryEnter(obj: object): boolean

Attempts to enter a critical section immediately without waiting.

Parameters:

  • obj - Any object to use as the critical section identifier

Returns:

  • boolean - true if successfully entered, false if already locked

Example:

if (criticalSection.tryEnter(myResource)) {
  // Got immediate access
  console.log('Entered critical section');
} else {
  // Resource is busy
  console.log('Resource unavailable');
}

criticalSection.waitLeave(obj: object, timeout?: number): Promise<boolean>

Waits for the critical section to be released without locking it. Unlike enter(), this method does not acquire the lock after waiting.

Parameters:

  • obj - Any object to wait for
  • timeout (optional) - Maximum time to wait in milliseconds. If not provided, waits indefinitely

Returns:

  • Promise<boolean> - Resolves to true when the critical section is released, false if timeout occurs

Example:

// Wait for resource to become available without locking it
const released = await criticalSection.waitLeave(myResource, 2000);
if (released) {
  // Resource is now available (but not locked by us)
  console.log('Resource is free');
} else {
  // Timeout occurred
  console.log('Resource still busy after 2 seconds');
}

criticalSection.isLocked(obj: object): boolean

Checks if the critical section for the specified object is currently locked.

Parameters:

  • obj - The object to check

Returns:

  • boolean - true if the critical section is locked, false otherwise

Example:

if (criticalSection.isLocked(myResource)) {
  console.log('Resource is currently locked');
} else {
  console.log('Resource is available');
}

criticalSection.leave(obj: object): void

Leaves the critical section for the given object, allowing queued entries to proceed.

Parameters:

  • obj - The object to leave the critical section for

Example:

criticalSection.leave(myResource);
// Critical section is now available for others

Usage Patterns

Protecting Async Operations

const database = { connection: 'db-pool' };

async function updateUser(userId: string, data: object) {
  const entered = await criticalSection.enter(database);

  if (entered) {
    try {
      const user = await db.findUser(userId);
      user.update(data);
      await user.save();
    } finally {
      criticalSection.leave(database);
    }
  }
}

Browser: Preventing Double-Click Issues

// Problem: Double-clicks can cause duplicate form submissions,
// leading to duplicate orders, payments, or data corruption
const submitButton = document.getElementById('submit-btn');

submitButton.addEventListener('click', async (event) => {
  if (criticalSection.tryEnter(submitButton)) {
    try {
      // These operations must complete as a unit
      await submitForm();
      showSuccessMessage();
    } finally {
      criticalSection.leave(submitButton);
    }
  } else {
    // Already processing - prevents duplicate submission
    console.log('Form submission already in progress');
  }
});

Browser: Global Object Synchronization

// Use document/window as locks for global operations
async function updateGlobalTheme(newTheme: string) {
  const entered = await criticalSection.enter(document, 1000);
  if (entered) {
    try {
      document.documentElement.setAttribute('data-theme', newTheme);
      await saveThemeToStorage(newTheme);
    } finally {
      criticalSection.leave(document);
    }
  }
}

// Prevent overlapping resize operations
// Without protection: rapid resize events could cause inconsistent UI state
// (e.g., canvas size updated but layout calculation still pending)
async function handleWindowResize() {
  if (criticalSection.tryEnter(window)) {
    try {
      // These 3 operations must complete atomically
      await recalculateLayout();
      await updateCanvasSize();
      await triggerRedraw();
    } finally {
      criticalSection.leave(window);
    }
  }
  // Skip if already processing - prevents UI corruption
}

Server: Rate Limiting with tryEnter

const rateLimiter = { endpoint: '/api/heavy-operation' };

async function handleRequest(req, res) {
  if (criticalSection.tryEnter(rateLimiter)) {
    try {
      // Process the request
      await processHeavyOperation(req, res);
    } finally {
      criticalSection.leave(rateLimiter);
    }
  } else {
    // Too many requests
    res.status(429).send('Rate limit exceeded');
  }
}

Timeout-based Operations

const slowResource = { name: 'slow-service' };

async function processWithTimeout() {
  const entered = await criticalSection.enter(slowResource, 3000);

  if (entered) {
    try {
      await performSlowOperation();
    } finally {
      criticalSection.leave(slowResource);
    }
  } else {
    // Handle timeout
    await fallbackOperation();
  }
}

Queue Management

const printQueue = { printer: 'office-printer' };

async function printDocument(document: string) {
  console.log(`Queuing document: ${document}`);

  // This will wait in line if printer is busy
  const entered = await criticalSection.enter(printQueue);

  if (entered) {
    try {
      console.log(`Printing: ${document}`);
      await simulatePrinting(document);
      console.log(`Finished: ${document}`);
    } finally {
      criticalSection.leave(printQueue);
    }
  }
}

// Multiple documents will print in order
printDocument('Report A');
printDocument('Report B');
printDocument('Report C');

Monitoring Resource Availability

const sharedCache = { name: 'user-cache' };

// Wait for cache to be free before doing cleanup
async function cleanupCache() {
  console.log('Waiting for cache to be released...');

  // Wait without locking - other operations can still use the cache
  const released = await criticalSection.waitLeave(sharedCache, 5000);

  if (released) {
    // Now we can safely check or perform non-critical operations
    if (!criticalSection.isLocked(sharedCache)) {
      console.log('Cache is free, starting cleanup...');
      // Perform cleanup operations
    }
  } else {
    console.log('Cache is still busy, will retry later');
  }
}

// Check status without affecting the lock
function getCacheStatus() {
  if (criticalSection.isLocked(sharedCache)) {
    return 'Cache is currently in use';
  } else {
    return 'Cache is available';
  }
}

How It Works

Uses a WeakMap to associate objects with their critical section state. Different objects = independent locks. When objects are garbage collected, their critical section state is automatically cleaned up.

const fileA = { path: '/tmp/fileA.txt' };
const fileB = { path: '/tmp/fileB.txt' };

await criticalSection.enter(fileA);  // ✅ Acquired
await criticalSection.enter(fileB);  // ✅ Also acquired (different object)

Compatibility

  • TypeScript: Full type definitions included
  • Browsers: Chrome 36+, Firefox 6+, Safari 7.1+, Edge 12+
  • Node.js: 12.0+
  • Modules: ES modules, CommonJS, all modern bundlers

License

MIT

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.