named-placeholders
npmv1.1.6sql named placeholders to unnamed compiler
Safe to adopt
Yes — named-placeholders scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 268 days ago. 2 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 268 days ago. 2 releases in the last 2 years.
- AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 7.0 KB installed (at least — some of the tree is still being crawled).
- 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 named-placeholders 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.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Compatibility
- Node.js
- node >=8.0.0
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the named-placeholders README.
var mysql = require('mysql');
var toUnnamed = require('named-placeholders')();
var q = toUnnamed('select 1+:test', { test: 123 });
mysql.createConnection().query(q[0], q[1]);named-placeholders 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 |
|---|---|---|---|---|
| named-placeholdersthis page | 0 | 1 | MIT | 8 months ago |
| drizzle-orm | 19M | 0 | Apache-2.0 | 1 day ago |
| kysely | 15.6M | 1 | MIT | 1 day ago |
| knex | 0 | 1 | MIT | 1 day ago |
| sql-escaper | 5M | 1 | MIT | 1 day ago |
| postgres | 0 | 1 | Unlicense | 1 day ago |
Dependencies
Declared by named-placeholders v1.1.6. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (2)
Used by
Popular packages that depend on named-placeholders.
Relationship graph
Dependencies (left) and dependents (right) of named-placeholders.
Frequently installed together
TypeScript definitions for node
Prettier is an opinionated code formatter
A Long class for representing a 64-bit two's-complement integer value.
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files
Module that helps you write generated functions in Node
🛡️ Faster SQL escape and format for JavaScript (Node.js, Bun, and Deno).
Convert character encodings in pure javascript.
AWS RDS SSL certificates bundles.
Extract meaning from JS Errors
The fastest javascript implementation of a double-ended queue. Used by the official Redis, MongoDB, MariaDB & MySQL libraries for Node.js and many other libraries. Maintains compatability with deque.
Release history
2 releases in the last two years, typically about 132 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.1.6latest | 8 months ago | 7.0 KB | MIT |
| 1.1.4 | 9 months ago | 6.7 KB | MIT |
| 1.1.3 | 3 years ago | 7.0 KB | MIT |
| 1.1.2 | 7 years ago | 7.5 KB | MIT |
| 1.1.1 | 10 years ago | — | MIT |
| 1.1.0 | 11 years ago | — | MIT |
| 1.0.0 | 11 years ago | — | MIT |
| 0.1.3 | 11 years ago | — | MIT |
| 0.1.2 | 11 years ago | — | MIT |
| 0.1.1 | 12 years ago | — | MIT |
| 0.1.0 | 12 years ago | — | MIT |
Overview
named-placeholders is an npm package that sql named placeholders to unnamed compiler. It has 1 known dependents in the graph. The latest version is 1.1.6, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need sql named placeholders to unnamed compiler and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
- Lean dependency tree (3 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use named-placeholders?
Yes — named-placeholders scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 268 days ago. 2 releases in the last 2 years.
How do I install named-placeholders?
Run `npm install named-placeholders` to add named-placeholders to your npm project.
How many dependencies does named-placeholders have?
named-placeholders declares 3 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 7.0 KB on disk.
What license is named-placeholders released under?
named-placeholders is distributed under the MIT license.
How popular is named-placeholders?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on named-placeholders.
Is named-placeholders still maintained?
The most recent release of named-placeholders (v1.1.6) was published 8 months ago.
Does named-placeholders run install scripts?
No. named-placeholders does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.