quansync
npmv1.0.0TypeScriptCreate sync/async APIs with usable logic
Safe to adopt
Yes — quansync scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 279 days ago. 22 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 279 days ago. 22 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 15 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 2 maintainers, and a contained dependency surface.
- 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 quansync 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.
Compatibility
- Node.js
- No constraint declared
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the quansync README.
import fs from 'node:fs'
import { quansync } from 'quansync'
// Create a quansync function by providing `sync` and `async` implementations
const readFile = quansync({
sync: (path: string) => fs.readFileSync(path),
async: (path: string) => fs.promises.readFile(path),
})
// Create a quansync function by providing a generator function
const myFunction = quansync(function* (filename) {
// Use `yield*` to call another quansync function
const code = yield* readFile(filename, 'utf8')
quansync 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 |
|---|---|---|---|---|
| quansyncthis page | 0 | 1 | MIT | 9 months ago |
| co | 46M | 4 | MIT | 5 days ago |
| async-foreach | 900.6K | 1 | — | 5 days ago |
| await-lock | 0 | 1 | MIT | 6 days ago |
| regenerator-runtime | 0 | 4 | MIT | 6 days ago |
| p-limit | 333.1M | 5 | MIT | 5 days ago |
Dependencies
Declared by quansync v1.0.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (13)
Used by
Popular packages that depend on quansync.
Relationship graph
Dependencies (left) and dependents (right) of quansync.
Frequently installed together
An AST-based pattern checker for JavaScript.
Next generation testing framework powered by Vite
Missing ECMAScript module utils for Node.js
TypeScript definitions for chai
Find a file or directory by walking up parent directories — Zero dependencies
Node.js utilities and TypeScript definitions for `package.json` and `tsconfig.json`
TypeScript definitions for node
BDD/TDD assertion library for node.js and the browser. Test framework agnostic.
Release history
22 releases in the last two years, typically about 0 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.0.0latest | 9 months ago | 15 KB | MIT |
| 0.3.0 | 9 months ago | 22 KB | MIT |
| 0.2.11 | 1 year ago | 24 KB | MIT |
| 0.2.10 | 1 year ago | 23 KB | MIT |
| 0.2.9 | 1 year ago | 23 KB | MIT |
| 0.2.8 | 1 year ago | 20 KB | MIT |
| 0.2.7 | 1 year ago | 20 KB | MIT |
| 0.2.6 | 1 year ago | 20 KB | MIT |
| 0.2.5 | 1 year ago | 19 KB | MIT |
| 0.2.4 | 1 year ago | 19 KB | MIT |
| 0.2.3 | 1 year ago | 19 KB | MIT |
| 0.2.2 | 1 year ago | 18 KB | MIT |
| 0.2.1 | 1 year ago | 18 KB | MIT |
| 0.2.0 | 1 year ago | 11 KB | MIT |
| 0.1.0 | 1 year ago | 11 KB | MIT |
Overview
quansync is an npm package that create sync/async APIs with usable logic. It has 1 known dependents in the graph. The latest version is 1.0.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need create sync/async APIs with usable logic and value a focused 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
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Funding
Frequently asked questions
Should I use quansync?
Yes — quansync scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 279 days ago. 22 releases in the last 2 years.
How do I install quansync?
Run `npm install quansync` to add quansync to your npm project.
What license is quansync released under?
quansync is distributed under the MIT license.
How popular is quansync?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on quansync.
Is quansync still maintained?
The most recent release of quansync (v1.0.0) was published 9 months ago.
Does quansync run install scripts?
No. quansync does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.