CommonJS: JavaScript Standard Library
CommonJS Modules This specification addresses how modules should be written in order to be interoperable among a class of module systems that can be both client and server side, secure or insecure, implemented today or supported by future systems with syntax extensions. These modules are offered privacy of their top scope, facility for importing singleton objects from other modules, and exporting
Unit Testing - CommonJS Spec Wiki
STATUS: 1.0 RATIFIED, AMENDMENT PROPOSALS PENDING Unit testing Automated tests are an important part of software development today. Providing a standard test library will help encourage more people to write more tests. Additionally, the API specification will likely be written in the form of tests, so this component will be needed by the CommonJS project itself. Testing involves both an API for ea
旧石器時代のJavaScriptを書いてる各位に告ぐ、現代的なJavaScript超入門 Section2 ～CommonJSモジュールと仲良くなろう～ - Qiita
はじめに この記事は「旧石器時代のJavaScriptを書いてる各位に告ぐ、現代的なJavaScript超入門」の2つ目の記事です。 シリーズの最初から読みたい方は 旧石器時代のJavaScriptを書いてる各位に告ぐ、現代的なJavaScript超入門 Section1 ～すぐにでも現代っぽく出来るワンポイントまとめ～ へどうぞ。 また、このシリーズではECMAScript5を概ね対応するブラウザを対象としています。 もっと平たくいうと、IE8以下は切り捨てます。ご了承ください。 そしてプロによるマサカリ 対策として一つ重要な注意書きをします。 この記事中で出てくる「CommonJSモジュール」という表現は全て「CommonJSのModules 1.0仕様をベースとして、Node.jsが独自に拡張したCommonJS派生のモジュール仕様及びインターフェース(require/exports
JSGI - CommonJS Spec Wiki
Web server to application interface A well-defined interface for connecting web applications to web servers is a very powerful thing. This approach has enabled applications written with any Java framework, for example, to be deployed behind a Java server ("servlet container"). Additionally, the standard interface allows the creation of "middleware", or software that sits in between the server and
Packages/1.1 - CommonJS Spec Wiki
This specification describes the CommonJS package format for distributing CommonJS programs and libraries. A CommonJS package is a cohesive wrapping of a collection of modules, code and other assets into a single form. It provides the basis for convenient delivery, installation and management of CommonJS components. This specifies the CommonJS package descriptor file and package file format. It do
CommonJS: JavaScript Standard Library
CommonJS API Current Specifications Proposals and standards in development // Formatting has been cleaned up around the site and on the Modules 1.0 page. // This website has been replaced with a new one backed by the wiki so it can be edited by the whole commonjs community. // We are no longer using the bulk 0.1 and 0.5 specification version numbers. Specs individually are marked as standards. Com
CommonJS: JavaScript Standard Library
CommonJS Modules This specification addresses how modules should be written in order to be interoperable among a class of module systems that can be both client and server side, secure or insecure, implemented today or supported by future systems with syntax extensions. These modules are offered privacy of their top scope, facility for importing singleton objects from other modules, and exporting
RDBMS - CommonJS Spec Wiki
Relational Database Interface Though there are many kinds of persistence engines available, relational databases are the most commonly deployed. Relational databases have a consistent data model and a reasonably consistent set of operations. This has allowed for the creation of a standard interface in many different languages. If it's possible to interface with other types of databases using the s
Unit Testing/1.0 - CommonJS Spec Wiki
STATUS: APPROVED BY DISCUSSION PARTICIPANTS Pardicipants Tom Robinson, Ash Berlin, George Moschovitis, Chris Zumbrunn, Hannes Wallnöfer, Kris Kowal, Kevin Dangoor, Ates Goral, and Davey Waterson (Discussion) Implementations [[Implementations/Flusspferd|]], [[Implementations/Narwhal|]] (0.2), [[Implementations/SproutCore|]], [[Implementations/node.js|]], [[Implementations/TeaJS|]], [[Implementation
Modules - CommonJS Spec Wiki
To date, client side JavaScript has generally been able to get away with something as simple as the <script> tag and no standard way to do namespaces. On the server, it's a bit different because you're more likely to use more libraries and you can potentially load up a lot of code. Having a basic system for loading code and encouraging the use of namespaces to avoid unintentional interference will
Modules/AsynchronousDefinition - CommonJS Spec Wiki
STATUS: PROPOSAL Implementations [[Implementations/RequireJS|]], [[Implementations/Nodules|]], [[Implementations/Yabble (partial)|]], [[Implementations/Dojo|]], [[Implementations/Transporter|]], [[Implementations/Teleport|]], [[Implementations/PINF (partial)|]], [[Implementations/curl.js|]] NOTE: This document is retained for historical purposes, but the evolution of this API is now tracked on the
Promises - CommonJS Spec Wiki
Promises provide a well-defined interface for interacting with an object that represents the result of an action that is performed asynchronously, and may or may not be finished at any given point in time. By utilizing a standard interface, different components can return promises for asynchronous actions and consumers can utilize the promises in a predictable manner. Promises can also provide the
Modules/1.0 - CommonJS Spec Wiki
STATUS: SUPERSEDED BY 1.1 Implementations [[Implementations/Flusspferd|]], [[Implementations/GLUEscript|]], [[Implementations/GPSEE|]], [[Implementations/JSBuild|]], [[Implementations/Narwhal|]] (0.1), [[Implementations/Persevere|]], [[Implementations/RingoJS|]], [[Implementations/SproutCore|]], [[Implementations/node.js|]], [[Implementations/TeaJS|]], [[Implementations/CouchDB|]], [[Implementatio
Packages/1.0 - CommonJS Spec Wiki
STATUS: RATIFIED Implementations [[Implementations/JSBuild|]], [[Implementations/PINF|]], [[Implementations/ArangoDB|]] This specification describes the CommonJS package format for distributing CommonJS programs and libraries. A CommonJS package is a cohesive wrapping of a collection of modules, code and other assets into a single form. It provides the basis for convenient delivery, installation a
JSGI/Level0/A/Draft2 - CommonJS Spec Wiki
Philosophy Straightforward but convenient mapping to HTTP and existing gateway interface conventions Suitable for extension with a defined mechanism for Extension Proposals Cosmetic modifications more inline with JavaScript conventions and idioms Principles Discourage duplicate data in request and response objects Optimize for the Application developer, not the Server or Middleware developer Adher
JSGI/Level0/A - CommonJS Spec Wiki
NOTE: the more recent version of this specification is Draft 2 JSGI Level 0 Proposal A, Draft 1 (in development) Philosophy A straightforward but more user friendly mapping to existing gateway interface conventions Suitable for extension via some forthcoming "Level 1" JSGI Addressing all known shortcomings that would be difficult to correct with a "Level 1" layer (header name mangling, header case
Modules/1.1 - CommonJS Spec Wiki
STATUS: MULTIPLE IMPLEMENTATIONS Implementations [[Implementations/Ejscript|]] (2.x), [[Implementations/Flusspferd|]] (0.9), [[Implementations/GPSEE|]], [[Implementations/Narwhal|]] (0.2), [[Implementations/Persevere|]] (?), [[Implementations/RingoJS|]], [[Implementations/SproutCore|]] (?), [[Implementations/TeaJS|]], [[Implementations/Wakanda|]], [[Implementations/SilkJS|]], [[Implementations/lit
Promises/A - CommonJS Spec Wiki
Proposal A promise represents the eventual value returned from the single completion of an operation. A promise may be in one of the three states, unfulfilled, fulfilled, and failed. The promise may only move from unfulfilled to fulfilled, or unfulfilled to failed. Once a promise is fulfilled or failed, the promise's value MUST not be changed, just as a values in JavaScript, primitives and object
CommonJS: JavaScript Standard Library
Getting CommonJS There are several implementations of the CommonJS standard, and you can choose the one that fits what you're trying to do. // Formatting has been cleaned up around the site and on the Modules 1.0 page. // This website has been replaced with a new one backed by the wiki so it can be edited by the whole commonjs community. // We are no longer using the bulk 0.1 and 0.5 specification
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Modules interop · Issue #95 · babel/babel
