Socket
Socket
Sign inDemoInstall

@jsenv/abort

Package Overview
Dependencies
0
Maintainers
2
Versions
18
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    @jsenv/abort

Help to write code compatible with abort signals


Version published
Weekly downloads
127
increased by9.48%
Maintainers
2
Install size
18.6 kB
Created
Weekly downloads
 

Changelog

Source

34.3.0

  • Add ability to inline file with "?inline" It can also be used to obtain js classic from js module with "?as_js_classic&inline"
  • Add importMap to Node.js runtimeParams (both child process and worker thread) Allow to redirect import to other files during tests (mocking)
  • Muliple --require= and --experimental-loader= passed to commandLineOptions are now preserved (Before the last one wins)
  • Prevent generating trailing comma on dynamic import during import assertion transpilation
  • Better indentation in html generated during dev and build
  • Internal dev experience improvements on file/directory snapshots

Readme

Source

Abort npm package

Help to write code accepting an abortSignal.

  • Designed to cleanup by default (removing event listeners, clearing timeouts, ...)
  • Allow to safely bypass max listeners warning when needed
    • Code can do 20 abortable fetch requests in parallel without warnings
  • Manage multiple abort signals
    • Compose abort signals from multiple sources
    • Code can do differents things depending on which signal aborted the operation

Example

fetch_demo.mjs

import { customFetch } from "./fetch_custom.mjs";

const abortController = new AbortController();
const signal = abortController.signal;
process.on("warning", () => {
  abortController.abort();
});
await customFetch("http://example.com", { signal });

Code above pass an abort signal to customFetch.

Let's see how "@jsenv/abort" helps to manage the signal received.

fetch_custom.mjs

import { Abort } from "@jsenv/abort"

export const customFetch = (
  url,
  { signal = new AbortController().signal } = {},
) => {
  // create an operation
  const fetchOperation = Abort.startOperation()

  // abort according to signal received in param
  fetchOperation.addAbortSignal(signal)

  // also abort on SIGINT
  const SIGINTAbortSource = fetchOperation.addAbortSource((abort) => {
    process.on("SIGINT", abort)
    return () => {
      process.removeListener("SIGINT", abort)
    }
  })

  // also abort after 5s
  const timeoutAbortSource = fetchOperation.timeout(5000)

  try {
    const response = await fetch(url, { signal: fetchOperation.signal })
    return response
  } catch (e) {
    if (Abort.isAbortError(e)) {
      if (SIGINTAbortSource.signal.aborted) {
        // aborted by SIGINT
      }
      if (timeoutAbortSource.signal.aborted) {
        // aborted by timeout
      }
      if (signal.aborted) {
        // aborted from outside
      }
    }
    throw e
  } finally {
    await fetchOperation.end()
  }
}

FAQs

Last updated on 12 Jan 2024

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc