Skip to content
This repository was archived by the owner on Jun 5, 2020. It is now read-only.

Commit

Permalink
README
Browse files Browse the repository at this point in the history
  • Loading branch information
Daniel Wirtz committed Mar 8, 2013
1 parent 3a176c0 commit f5fbb31
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
Binary file added NodejsClosureCompilerExterns.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
node.js Closure Compiler externs [![Build Status](https://travis-ci.org/dcodeIO/node.js-closure-compiler-externs.png?branch=master)](https://travis-ci.org/dcodeIO/node.js-closure-compiler-externs)
![node.js Closure Compiler externs](https://raw.github.com/dcodeIO/node.js-closure-compiler-externs/master/NodejsClosureCompilerExterns.png)
================================
A collection of node.js externs for use with [Closure Compiler](https://developers.google.com/closure/compiler/docs/overview)
/ [ClosureCompiler.js](https://github.com/dcodeIO/ClosureCompiler.js).
Expand Down Expand Up @@ -40,7 +40,7 @@ var EventEmitter = events.EventEmitter;
If a file requires a dependency, it is named in the `@fileoverview` declaration. You should then include the dependency
in your compile step, too.

Testing
Testing [![Build Status](https://travis-ci.org/dcodeIO/node.js-closure-compiler-externs.png?branch=master)](https://travis-ci.org/dcodeIO/node.js-closure-compiler-externs)
-------
Externs are automatically syntax-validated through a [ClosureCompiler.js](https://github.com/dcodeIO/ClosureCompiler.js)
test run. This does not imply that the extern is complete or does actually represent the underlying API (but it should).
Expand Down

0 comments on commit f5fbb31

Please sign in to comment.