synckit
npmv0.11.13TypeScriptPerform async work synchronously in Node.js using `worker_threads` with first-class TypeScript support.
Safe to adopt
Yes — synckit scores well across adoption, maintenance, weight, supply chain, and licensing. 45.3M downloads per week and 1 known dependents. Last published 105 days ago. 20 releases in the last 2 years.
- AAdoption: grade A, Excellent.
45.3M downloads per week and 1 known dependents.
- BMaintenance: grade B, Good.
Last published 105 days ago. 20 releases in the last 2 years.
- AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 107 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding synckit to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Licenses in the dependency tree
Every license you inherit by installing synckit, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node ^14.18.0 || >=16.0.0
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the synckit README.
// runner.js
import { createSyncFn } from 'synckit'
// the worker path must be absolute
const syncFn = createSyncFn(require.resolve('./worker'), {
tsRunner: 'tsx', // optional, can be `'node' | 'ts-node' | 'esbuild-register' | 'esbuild-runner' | 'tsx'`
})
// do whatever you want, you will get the result synchronously!
const result = syncFn(...args)synckit vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| synckitthis page | 45.3M | 1 | MIT | 3 months ago |
| async-foreach | 643.2K | 1 | — | 1 day ago |
| quansync | 0 | 1 | MIT | 1 day ago |
| globule | 0 | 1 | MIT | 1 day ago |
Dependencies
Declared by synckit v0.11.13. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Used by
Popular packages that depend on synckit.
Relationship graph
Dependencies (left) and dependents (right) of synckit.
Frequently installed together
Prettier is an opinionated code formatter
This packages is a collection of utilities and helper functions
No description provided.
This package contains shared types of Jest's packages.
Babel Types is a Lodash-esque utility library for AST nodes
Stringify any JavaScript value.
No description provided.
Display differences clearly so people can review changes confidently.
A set of utility functions for expect and related packages
Allow parsing of TypeScript syntax
A Babel preset that enables parsing of proposals supported by the current Node.js version.
Turns an AST into code.
Release history
19 releases in the last two years, typically about 3 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 0.11.13latest | 3 months ago | 95 KB | MIT |
| 0.11.12 | 7 months ago | 95 KB | MIT |
| 0.11.11 | 1 year ago | 96 KB | MIT |
| 0.11.10 | 1 year ago | 96 KB | MIT |
| 0.11.8 | 1 year ago | 96 KB | MIT |
| 0.10.4 | 1 year ago | 77 KB | MIT |
| 0.9.3 | 1 year ago | 59 KB | MIT |
| 0.11.7 | 1 year ago | 96 KB | MIT |
| 0.11.6 | 1 year ago | 96 KB | MIT |
| 0.11.5 | 1 year ago | 96 KB | MIT |
| 0.11.4 | 1 year ago | 91 KB | MIT |
| 0.11.3 | 1 year ago | 91 KB | MIT |
| 0.11.2 | 1 year ago | 91 KB | MIT |
| 0.11.1 | 1 year ago | 91 KB | MIT |
| 0.11.0 | 1 year ago | 91 KB | MIT |
Overview
synckit is an npm package that perform async work synchronously in Node.js using `worker_threads` with first-class TypeScript support. It is extremely widely used, with about 45.3M downloads per week and 1 known dependents in the graph. The latest version is 0.11.13, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need perform async work synchronously in Node.js using `worker_threads` with first-class TypeScript support and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Large, well-established user base (45.3M weekly downloads).
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
- Lean dependency tree (1 direct dependencies).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Funding
Frequently asked questions
Should I use synckit?
Yes — synckit scores well across adoption, maintenance, weight, supply chain, and licensing. 45.3M downloads per week and 1 known dependents. Last published 105 days ago. 20 releases in the last 2 years.
How do I install synckit?
Run `npm install synckit` to add synckit to your npm project.
How many dependencies does synckit have?
synckit declares 1 direct dependency and pulls in 1 packages in total once its runtime tree is resolved totalling about 107 KB on disk.
What license is synckit released under?
synckit is distributed under the MIT license.
How popular is synckit?
synckit has approximately 45,304,493 downloads per week and 1 known dependent packages.
Is synckit still maintained?
The most recent release of synckit (v0.11.13) was published 3 months ago.
Does synckit run install scripts?
No. synckit does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.