Displaying 1 to 20 from 30 results

jsdom - A JavaScript implementation of the WHATWG DOM and HTML standards, for use with node.js

  •    Javascript

jsdom is a pure-JavaScript implementation of many web standards, notably the WHATWG DOM and HTML Standards, for use with Node.js. In general, the goal of the project is to emulate enough of a subset of a web browser to be useful for testing and scraping real-world web applications.As of v10, jsdom has a new API (documented below). The old API is still supported for now; see its documentation for details.

postcss-preset-env - Convert modern CSS into something browsers understand

  •    CSS

PostCSS Preset Env lets you convert modern CSS into something most browsers can understand, determining the polyfills you need based on your targeted browsers or runtime environments. Without any configuration options, PostCSS Preset Env enables Stage 2 features and supports all browsers.

xmldom - A PURE JS W3C Standard based(XML DOM Level2 CORE) DOMParser and XMLSerializer.

  •    Javascript

A JavaScript implementation of W3C DOM for Node.js, Rhino and the browser. Fully compatible with W3C DOM level2; and some compatible with level3. Supports DOMParser and XMLSerializer interface such as in browser.

csstree - A tool set for working with CSS including fast detailed parser, walker, generator and lexer based on W3C specs and browser implementations

  •    Javascript

CSSTree is a tool set to work with CSS, including fast detailed parser (string->AST), walker (AST traversal), generator (AST->string) and lexer (validation and matching) based on knowledge of spec and browser implementations. The main goal is to be efficient and W3C spec compliant, with focus on CSS analyzing and source-to-source transforming tasks. NOTE: The project is in alpha stage since some parts need further improvements, AST format and API are subjects to change. However it's stable enough and used by packages like CSSO (CSS minifier) and SVGO (SVG optimizer) in production.




respec - A tool for creating technical documents and web standards

  •    Javascript

ReSpec is a JS library that makes it easier to write technical specifications, or documents that tend to be technical in nature in general. It was originally designed for the purpose of writing W3C specifications, but has since grown to be able to support other outputs as well. If you are just interested in writing a spec, you can grab the starter spec.

node-Tor - Javascript implementation of the Tor (or Tor like) anonymizer project (The Onion Router)

  •    Javascript

For a quick look, see the demo video on Peersm, download and stream anonymously inside your browser, serverless anonynous P2P network compatible with torrents. Check out torrent-live for a more general presentation and to get the dynamic blocklist.

platform-status - Project Platform Status

  •    Javascript

Platform Status gives developers a cross-platform and cross-browser roadmap for browser features, from standardization and development to release. Not only a channel to raise awareness, it can also drive adoption and improve the vital feedback loop Firefox's platform needs to have with web developers. For most developers it will be a reference to discover and learn, but it has the potential to provide the entry points for radical participation on Mozilla's platform development.Existing web compatibility references, like caniuse focus on cross-browser compatibility but don't cover un-released features and lag behind on features that already shipped. Major browser vendors (Edge, Chrome, Webkit) are publicising their own platform status with references to their bug tracking and bug owners. Similar to Platform Status' goal, Chrome tracks consensus/enthusiasm from other browsers using sources that range from bugs, to IRC logs to tweets.

gulp-w3cjs - :vertical_traffic_light: w3cjs wrapper for gulp to validate your HTML

  •    Javascript

The results are also added onto each file object under w3cjs, containing success (Boolean) and messages (Array). URL to the w3c validator. Use if you want to use a local validator. This is the same thing as w3cjs.setW3cCheckUrl().


html-tags - List of standard HTML tags

  •    Javascript

It's just a couple of JSON files that can be used in any environment.It intentionally leaves out obsolete tags.

node-elf-logger - A Node

  •    Javascript

This library is a simple, configurable, node.js HTTP server compatible logging implementation that complies with the W3C's Extended Log File Format. Major HTTP servers like IIS and Apache have options to follow this logging format, and that has the advantage of log viewing software that has already been written for this format.dir: The root directory where node-elf-logger should store it's log files. This value will be prefixed onto the template value if present.

SCION - SCXML Interpretation and Optimization eNgine

  •    Javascript

SCION is an industrial-strength implementation of W3C SCXML in JavaScript. SCXML provides a declarative markup for Statecharts, a powerful modelling language for developing complex, timed, event-driven, state-based systems.

SCION-CORE - A minimal implementation of Statecharts in portable, embeddable JavaScript.

  •    Javascript

SCION-CORE is a small implementation of Statecharts in ECMAScript (JavaScript). SCION-CORE lets you program with Statecharts using a simple JavaScript/JSON API. SCION-CORE is then available as the global variable scion.

scxml-test-framework - A set of SCXML tests, and an HTTP client test runner for testing against SCXML HTTP test servers

  •    Javascript

This test script indicates that after SCXML document basic/basic1.scxml is loaded into the SCXML interpreter, the expected initial configuration of the state machine will be a single state with id "a". Next, an event with name "t" and no data will be dispatched on the state machine, and the resulting state machine configuration will be a single state with id "b". Note that the "initialConfiguration" and "nextConfiguration" properties should only contain the ids of expected basic states, which is to say "initialConfiguration" and "nextConfiguration" specify a "basic configuration", or a configuration of basic states. As a "full configuration", or a configuration composed of both basic and non-basic states, can be derived from a basic configuration, specifying only basic configurations in the test script can be done without leading to a loss of safety or generality.

css-validator - Validate CSS via W3C's service

  •    Javascript

This was created to validate CSS inside of the json2css test suite. If cb is not provided, a DuplexStream will be returned to you.

postcss-preset-env - Convert modern CSS into something browsers understand

  •    Javascript

PostCSS Preset Env lets you convert modern CSS into something most browsers can understand, determining the polyfills you need based on your targeted browsers or runtime environments. Without any configuration options, postcss-preset-env enables stage 3 features and supports all browsers.

w3c-validate - Validates web content using the W3C's validation service

  •    Javascript

A node.js library for testing web responses against the w3c html validator. Inspired by w3cjs, but based purely on buffers. Use with your tests.

event-target-shim - An implementation of WHATWG EventTarget interface, plus few extensions.

  •    Javascript

An implementation of WHATWG EventTarget interface, plus few extensions. Use npm to install then use a bundler.

scribejs - Converter of RRSAgent IRC logs into minutes in markdown

  •    Javascript

This script takes an IRC output as produced by the RRSAgent on W3C’s IRC, and converts into into minutes in markdown. Most of the features of David Booth's script are retained. See also a separate feature summary for an easier reference. The IRC log can either be provided as an input to the script on the command line, or can be fetched directly from the W3C site. The generated minutes are either stored locally or are committed to a GitHub repository directly. The reason of writing this script is that the current approach of producing HTML minutes on the W3C date space has become difficult to handle these days when Working Groups typically work on GitHub and WG members do not have CVS access to W3C. This means that the current process relies heavily on the staff contact on the slightest possible change of the minutes. In a GitHub working environment the “obvious” approach is to produce the minutes in markdown and push that onto the group’s repository; if so, the minutes can be read and, if necessary, updated, changed, improved, etc, by other Group members.





We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.