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

@amag-ch/sap_cap_common_jobs

v3.0.1

Published

Wrapper for cds.spawn with additional functionality

Downloads

182

Readme

sap_cap_common_jobs

npm version npm downloads

Wrapper for cds.spawn with additional functionality

Table of Contents

Features

  • Block jobs to avoid parallel processing
  • Set context id to job for better monitoring
  • Background jobs

Installing

Using npm:

$ npm install @amag-ch/sap_cap_common_jobs

Using yarn:

$ yarn add @amag-ch/sap_cap_common_jobs

Implementation

const jobs = require('@amag-ch/sap_cap_common_jobs')

jobs.spawn({ every: 1000, blockingId: 'a-blocking-id' }, async () => {
    // do something
})

A background job need two processing functions, called selector and executer, which must be given at construction. The job calls the selector and calls afterthen the executer with the selected entries. The job finish, if the selector didn't return any entries. Therefore it's needed to start the job again after the source of the selector have changed.

The job automaticly starts the first time after the cds server is up and running.

If the selector or executer produces an error, the jobs stopps and reschedule after a defined delay (default: 60000)

The name or the delay could be changed in the third argument of the constructor.

const { BackgroundJob } = require('@amag-ch/sap_cap_common_jobs')

const job = new BackgroundJob(
    async () => db.read('Table').limit(10).forUpdate(),
    async (entries) => console.log(entries)
)

job.start() // only possible, if current cds.context is set

License

MIT