The ExpressJS Organization is a collection of community-owned node.js web modules with shared maintenance. Refactored from Connect, Express, and Koa, these modules aim to be small, well-tested, focused, RFC-compliant, and usable by any node.js framework or middleware.
Please let us know if you're interested in:
- Maintaining some modules in the organization
- Moving popular libraries into the organization
Most of these libraries are based on many of TJ Holowaychuk's work. Maintainers were slowly added to his projects to keep up with the maintenance burden. But code maintenance isn't the sole issue; maintaining the repositories themselves as well their maintainers is just as difficult.
GitHub organizations allow easy administration of multiple repositories, their maintainers, as well as maintenance of their code. With TJ Holowaychuk's retirement from node.js, a robust framework to maintain his still widely-used modules is needed by the community, and GitHub organizations are the answer. With the ability to share npm publishing rights very easily, no (still useful) module will be left behind.
With organizations comes a change in node's open source authorship philosophy. npm places emphasis on the owner and author of a package. Instead, we believe open source software should be community owned and maintained as the original author is largely irrelevant if s/he no longer maintains the project. With organizations, users won't have to worry about code rot, ignored pull requests, or a single, overbearing czar.
These modules need maintainers. If you're interested in maintaining one of these modules, please start contributing by making PRs and solving / discussing unsolved issues.
- express-session - maintained, but needs a rewrite
- express-resource
- express-expose
- express-messages
- express-namespace
- express-params
These are the core team members, those that actively maintain more than one module. You can also view all the public team members.
- dougwilson - current lead maintainer of Express and Connect. Maintains much of Connect 2.x/Express 3.x's middleware as well as many tiny modules. A stickler for RFC-compliance, tests, and code-coverage.
- jonathanong - maintains many of the core modules as well as Koa
- fishrock123 - administrates and book-keeps many of the modules as well as maintains the mime-type-related libraries.
- defunctzombie
- mscdex
- visionmedia - maintains koa and co-related libraries
These frameworks are actively maintained by members of the Organization.
Building a node.js web framework? These are the modules you should be particularly interested in:
- accepts - high-level content negotiation
- csrf-tokens - the logic behind CSRF tokens
- cookies - cookie management with support for signed, base64-encoded, and encrypted cookies
- compressible - check whether a specific mime type is compressible
- finished - make sure you don't leak file descriptors
- media-typer - RFC-compliant media type parser
- mime-types - essentially a fork of mime
- path-to-regexp - path parser used by Express. Also supports the browser.
- resolve-path - check for malicious paths
- statuses - status code utility
- type-is - high-level
Content-Typechecking - vary -
Vary-header management
Our goal for open source software is to organize modules well as well as share the maintenance burden so that no one has to worry about code rot. The ExpressJS Organization is focused with node web modules, but there are multiple organizations maintained in a similar manner.
If you're interested in joining or collaborating with these organizations, please let us know!
- CoJS - co-related modules
- Component - browser components
- KoaJS - koa and associated middleware
- ReworkCSS - the rework CSS preprocessor and associated plugins
Organizations for tiny utilities:
- css-utils - generic CSS utilities
- crypto-utils - node cryptography-related modules
- fs-utils - file-system-related node modules
- math-utils - math utilities for both the server and the browser
- mongodb-utils - mongodb-related utilities
- repo-utils - utilities for repositories and packages
- stream-utils - node stream utilities
Other organizations you might be interested in:
- detects - browser feature detects as tiny modules
- node-modules - generic node modules
- normalize - package management-less, build-less, and specification-compliant web development
- polyfills - browser polyfills and user-agent-based polyfill combinations