Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/defer-run/defer.client
Zero infrastructure Node.js background jobs
https://github.com/defer-run/defer.client
background-jobs cron nodejs queueing typescript
Last synced: about 2 months ago
JSON representation
Zero infrastructure Node.js background jobs
- Host: GitHub
- URL: https://github.com/defer-run/defer.client
- Owner: defer-run
- License: isc
- Created: 2022-11-16T11:02:03.000Z (almost 2 years ago)
- Default Branch: master
- Last Pushed: 2024-03-06T10:31:39.000Z (7 months ago)
- Last Synced: 2024-04-23T09:26:08.354Z (5 months ago)
- Topics: background-jobs, cron, nodejs, queueing, typescript
- Language: TypeScript
- Homepage: https://www.defer.run/docs/introduction
- Size: 858 KB
- Stars: 210
- Watchers: 3
- Forks: 4
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
Zero infrastructure Node.js background jobs
Documentation
·
Blog
·
Community
·
Roadmap / RFCs
## Get started
- [Next.js Quickstart](https://docs.defer.run/get-started/quickstart/nextjs)
- [Express/Koa/hapi Quickstart](https://docs.defer.run/get-started/quickstart/express-koa-hapi)## API documentation
- [Retries](https://docs.defer.run/features/retries)
- [Delayed Function](https://docs.defer.run/features/delays)
- [CRON](https://docs.defer.run/features/cron)## Contributing
You want to fix a bug or suggest a change? Please open a PR! Want to
pitch a new feature, [please open a
RFC](https://github.com/defer-run/defer.client/discussions/new?category=roadmap).### Open a PR
Make sure to follow our [Code of Conduct](./CODE_OF_CONDUCT.md) and
the following requirements:1. Each new feature should be shipped with new tests
1. A PR should contains a description explaining the motivation### Local setup
1. Clone the repository: `git clone
[email protected]:defer-run/defer.client.git`
2. Install the dependencies: `npm ci`
3. Run the test after introducing changes: `npm run test`
4. Bump a patch or minor by running `npx changelog` (please provide a
brief description of the changes)