connect
npmv3.7.0High performance middleware framework
Not recommended for new projects
No — connect should not be adopted for new projects. Last published 2672 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 2672 days ago.
- BWeight: grade B, Good.
Pulls in 10 transitive packages, about 201 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 connect 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 connect, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >= 0.10.0
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the connect README.
var connect = require('connect');
var http = require('http');
var app = connect();
// gzip/deflate outgoing responses
var compression = require('compression');
app.use(compression());
// store session state in browser cookie
var cookieSession = require('cookie-session');
app.use(cookieSession({
keys: ['secret1', 'secret2']
}));connect vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
Dependencies
Declared by connect v3.7.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (4)
Used by
Popular packages that depend on connect.
Native-ESM powered web dev build tool
Minimal H(TTP) framework built for high performance and portability.
The Expo CLI
Dev server middleware for React Native
🚇 The JavaScript bundler for React Native.
🚇 Config parser for Metro.
No description provided.
Relationship graph
Dependencies (left) and dependents (right) of connect.
Frequently installed together
Expo Router is a file-based router for React Native and web applications.
The Expo SDK
TypeScript definitions for node
TypeScript-first schema declaration and validation library with static type inference
Lightweight debugging utility for Node.js and the browser
Blazing fast and accurate glob matcher written in JavaScript, with no dependencies and full support for standard and extended Bash glob features, including braces, extglobs, POSIX brackets, and regular expressions.
Stringify any JavaScript value.
TypeScript definitions for ws
Higher-level content negotiation
Get details about the current Continuous Integration environment
Better streaming static file server with Range and conditional-GET support
Create clickable links in the terminal
Release history
No releases in the last two years, typically about 35 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 3.7.0latest | 7 years ago | 93 KB | MIT |
| 3.6.6 | 8 years ago | 93 KB | MIT |
| 3.6.5 | 9 years ago | — | MIT |
| 3.6.4 | 9 years ago | — | MIT |
| 3.6.3 | 9 years ago | — | MIT |
| 3.6.2 | 9 years ago | — | MIT |
| 3.6.1 | 9 years ago | — | MIT |
| 3.6.0 | 9 years ago | — | MIT |
| 3.5.1 | 9 years ago | — | MIT |
| 3.5.0 | 10 years ago | — | MIT |
| 3.4.1 | 10 years ago | — | MIT |
| 2.30.2 | 11 years ago | — | MIT |
| 2.30.1 | 11 years ago | — | MIT |
| 3.4.0 | 11 years ago | — | MIT |
| 2.30.0 | 11 years ago | — | MIT |
Overview
connect is an npm package that high performance middleware framework. It has 7 known dependents in the graph. The latest version is 3.7.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need high performance middleware framework 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).
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 connect?
No — connect should not be adopted for new projects. Last published 2672 days ago.
How do I install connect?
Run `npm install connect` to add connect to your npm project.
How many dependencies does connect have?
connect declares 8 direct dependencies and pulls in 10 packages in total once its runtime tree is resolved totalling about 201 KB on disk.
What license is connect released under?
connect is distributed under the MIT license.
How popular is connect?
npm does not publish download counts. Within PackageGraph's crawl, 7 known packages depend on connect.
Is connect still maintained?
The most recent release of connect (v3.7.0) was published 7 years ago.
Does connect run install scripts?
No. connect does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.