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

jsworkerutils

v1.1.7

Published

Helper class that improves the the loading processes, an implementation of multithreaded JS # Development Guide ## About - This library is meant to be a node packaged module that optimize concurrent api requests and simplify as much as possible , the li

Downloads

17

Readme

flexloaders

DISCLAIMER: This library is a work in progress and its not ready for production

  • The whole paradigm of JavaScript is based on the idea of single-threaded environment but here come Web Workers which remove (partially) this limitation.Web Workers allow developers to put long-running and computationally intensive tasks on the background. This library simplifies the implementation of webworker for mutithreaded processes.
  • To use this library at this stage in your existing apps you might need to tweak some parts of the library
  • Improves the the loading process of endpoints on multiple processes
  • Runs multiple processes in parallel.
  • Targets es6, es2015, es5, Typescript
  • Primarily focuses on running multiple api request in parallel
    • On the client side
    • This library is meant to be a node packaged module that optimize concurrent api requests and simplify as much as possible , the library should be able integrate with other javascript projects indepent of frameworks.

Collaborrative Guide

  • Collaborators are welcome to fork this project please read the DevelopersREADME.md form guides
  • Optimize computational resource for running asynchronous requests
  • For web applications that requires loading multiple resources this library will help optimize calls

Use Case

  • import the library from conncurrent request from flexloaders
    import { concurrentRequests,layersSt} from 'flexloaders'
    concurrentRequest(< array of values >)

or common js

    const concurrentRequests = require('flexloaders');
    const layersSt = require('flexloaders');
  • All requests must be labelled with a layername and a url as declared below

    const req = {layername: <string>, url : <string>}

  • Pass all requests to an array and call as follows

    concurrentRequests([reqArray])

  • You can get the values of your request by subscibing to an observer which you imported above as

   layerSt
   layersSt.subscribe((item: any) =>
  • Check for values in your stream before accessing them as follows

    • You must also define a means to check if values are different before passing them as observable might stream same values over repeated calls
        if (Object.keys(item).length > 0  {
             item becomes your return value 
        }
  • All requests uses web workers hence cutting request time by a fraction of number of cores available on the client machine