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

@beyond-js/dynamic-processor

v0.0.3

Published

## Introduction

Downloads

182

Readme

@beyond-js/dynamic-processor

Introduction

The context on which the DynamicProcessor is designed, is when there is an asynchronous processing, and where you want to access the processed data synchronously, once the asynchronous processing has finished.

The general logic of the processor is that it starts in an inactive state, and once started, it is kept up-to-date by processing each time it is invalidated and as long as it has already been started. As the consumption of the DynamicProcessor data is synchronous, the data must be consumed after waiting for the .ready promise, or after receiving change notifications ('change' event). The 'change' event guarantees that the data has already been previously processed.

Processor usage is as follows:

1- Access the .ready property

  • await processor.ready;

2- Listen for changes

  • processor.on ('change', listener);

Characteristics

  • The processor does not execute processing until it is initialized.
  • If the .ready property (await processor.ready) is accessed, the processor is initialized, therefore processing is executed.
  • If the processor is invalidated, and it has already been initialized, then the .process method is executed automatically.
  • It emits change events every time it is processed again, starting from the second processing. The first processing is considered the initial state, and each additional processing, a change of the state of the processor.

Considerations

  • The initialise() method internally calls the _process() method. The processor is considered initialized when it has already been processed for the first time.

Problems that DynamicProcessor solves

  • Invalidating the object (execute ._invalidate()) implies reprocessing it, but only if it has already been initialized.
  • The _process (request) method receives the request parameter that allows, after executing any asynchronous function, to verify if it should continue processing or cancel the execution.
_process(request) {
  await asyncMethod ();
  if (this._request! == request) return; // Cancel execution
}
  • If the object is invalidated while processing, DynamicProcessor rerun the _process method automatically.

License

MIT © [BeyondJS]