pdf-creator-node 2.2.3 → 2.3.5

package/example/node_modules/pdf-creator-node/example/node_modules/jsprim/package.json

@@ -0,0 +1,20 @@
+{
+	"name": "jsprim",
+	"version": "1.4.2",
+	"description": "utilities for primitive JavaScript types",
+	"main": "./lib/jsprim.js",
+	"repository": {
+		"type": "git",
+		"url": "git://github.com/joyent/node-jsprim.git"
+	},
+	"dependencies": {
+		"assert-plus": "1.0.0",
+		"extsprintf": "1.3.0",
+		"json-schema": "0.4.0",
+		"verror": "1.10.0"
+	},
+	"engines": {
+		"node": ">=0.6.0"
+	},
+	"license": "MIT"
+}

package/example/node_modules/pdf-creator-node/example/node_modules/kew/.travis.yml

@@ -0,0 +1,5 @@
+language: node_js
+node_js:
+  - "0.12"
+  - "0.10"
+

package/example/node_modules/pdf-creator-node/example/node_modules/kew/LICENSE.TXT

@@ -0,0 +1,194 @@
+Copyright 2012 The Obvious Corporation.
+http://obvious.com/
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+
+
+-------------------------------------------------------------------------
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS

package/example/node_modules/pdf-creator-node/example/node_modules/kew/README.md

@@ -0,0 +1,320 @@
+kew: a lightweight (and super fast) promise/deferred framework for node.js
+==================================
+
+[![Build Status](https://travis-ci.org/Medium/kew.svg)](https://travis-ci.org/Medium/kew)
+
+**kew** is a lightweight promise framework with an aim of providing a base set of functionality similar to that provided by the [Q library](https://github.com/kriskowal/q "Q").
+
+A few answers (for a few questions)
+-------
+
+*Why'd we write it?*
+
+During our initial usage of **Q** we found that it was consuming 80% of the cpu under load (primarily in chained database callbacks). We spent some time looking at patching **Q** and ultimately found that creating our own lightweight library for server-usage would suit our needs better than figuring out how to make a large cross-platform library more performant on one very specific platform.
+
+*So this does everything Q does?*
+
+Nope! **Q** is still an awesome library and does *way* more than **kew**. We support a tiny subset of the **Q** functionality (the subset that we happen to use in our actual use cases).
+
+What are Promises?
+-------
+
+At its core, a *Promise* is a promise to return a value at some point in the future. A *Promise* represents a value that will be (or may return an error if something goes wrong). *Promises* heavily reduce the complexity of asynchronous coding in node.js-like environments. Example:
+
+```javascript
+// assuming the getUrlContent() function exists and retrieves the content of a url
+var htmlPromise = getUrlContent(myUrl)
+
+// we can then filter that through an http parser (our imaginary parseHtml() function) asynchronously (or maybe synchronously, who knows)
+var tagsPromise = htmlPromise.then(parseHtml)
+
+// and then filter it through another function (getLinks()) which retrieves only the link tags
+var linksPromise = tagsPromise.then(getLinks)
+
+// and then parses the actual urls from the links (using parseUrlsFromLinks())
+var urlsPromise = linksPromise.then(parseUrlsFromLinks)
+
+// finally, we have a promise that should only provide us with the urls and will run once all the previous steps have ran
+urlsPromise.then(function (urls) {
+  // do something with the urls
+})
+```
+
+How do I use **kew**?
+-------
+
+As a precursor to all the examples, the following code must be at the top of your page:
+
+```javascript
+var Q = require('kew')
+```
+
+### Convert a literal into a promise
+
+The easiest way to start a promise chain is by creating a new promise with a specified literal using Q.resolve() or Q.reject()
+
+```javascript
+// create a promise which passes a value to the next then() call
+var successPromise = Q.resolve(val)
+
+// create a promise which throws an error to be caught by the next fail() call
+var failPromise = Q.reject(err)
+```
+
+In addition, you can create deferreds which can be used if you need to create a promise but resolve it later:
+
+```javascript
+// create the deferreds
+var successDefer = Q.defer()
+var failDefer = Q.defer()
+
+// resolve or reject the defers in 1 second
+setTimeout(function () {
+  successDefer.resolve("ok")
+  failDefer.reject(new Error("this failed"))
+}, 1000)
+
+// extract promises from the deferreds
+var successPromise = successDefer.promise
+var failPromise = failDefer.promise
+```
+
+If you have a node-style callback (taking an **Error** as the first parameter and a response as the second), you can call the magic `makeNodeResolver()` function on a defer to allow the defer to handle the callbacks:
+
+```javascript
+// create the deferred
+var defer = Q.defer()
+
+// some node-style function
+getObjectFromDatabase(myObjectId, defer.makeNodeResolver())
+
+// grab the output
+defer.promise
+  .then(function (obj) {
+    // successfully retrieved the object
+  })
+  .fail(function (e) {
+    // failed retrieving the object
+  })
+```
+
+### Handling successful results with `.then()`
+
+When a promise is resolved, you may call the `.then()` method to retrieve the value of the promise:
+
+```javascript
+promise.then(function (result) {
+  // do something with the result here
+})
+```
+
+`.then()` will in turn return a promise which will return the results of whatever it returns (asynchronously or not), allowing it to be chained indefinitely:
+
+```javascript
+Q.resolve('a')
+  .then(function (result) {
+    return result + 'b'
+  })
+  .then(function (result) {
+    return result + 'c'
+  })
+  .then(function (result) {
+    // result should be 'abc'
+  })
+```
+
+In addition, `.then()` calls may return promises themselves, allowing for complex nesting of asynchronous calls in a flat manner:
+
+```javascript
+var htmlPromise = getUrlContent(myUrl)
+
+var tagsPromise = htmlPromise.then(function (html) {
+  if (!validHtml(html)) throw new Error("Invalid HTML")
+
+  // pretend that parseHtml() returns a promise and is asynchronous
+  return parseHtml(html)
+})
+```
+
+### Handling errors with `.fail()`
+
+If a promise is rejected for some reason, you may handle the failure case with the `.fail()` function:
+
+```javascript
+getObjectPromise
+  .fail(function (e) {
+    console.error("Failed to retrieve object", e)
+  })
+```
+
+Like `.then()`, `.fail()` also returns a promise. If the `.fail()` call does not throw an error, it will pass the return value of the `.fail()` handler to any `.then()` calls chained to it:
+
+```javascript
+getObjectPromise
+  .fail(function (e) {
+    return retryGetObject(objId)
+  })
+  .then(function (obj) {
+    // yay, we received an object
+  })
+  .fail(function (e) {
+    // the retry failed :(
+    console.error("Retrieving the object '" + objId + "' failed")
+  })
+})
+```
+
+If you've reached the end of your promise chain, you may call `.end()` which signifies that the promise chain is ended and any errors should be thrown in whatever scope the code is currently in:
+
+```javascript
+getObjectPromise
+  // this will throw an error to the uncaught exception handler if the getObjectPromise call is asynchronous
+  .end()
+```
+
+### `.fin()` when things are finished
+
+You may attach a handler to a promise which will be ran regardless of whether the promise was resolved or rejected (but will only run upon completion). This is useful in the cases where you may have set up resources to run a request and wish to tear them down afterwards. `.fin()` will return the promise it is called upon:
+
+```javascript
+var connection = db.connect()
+
+var itemPromise = db.getItem(itemId)
+  .fin(function () {
+    db.close()
+  })
+```
+
+Other utility methods
+-------
+
+### `.all()` for many things
+
+If you're waiting for multiple promises to return, you may pass them (mixed in with literals if you desire) into `.all()` which will create a promise that resolves successfully with an array of the results of the promises:
+
+```javascript
+var promises = []
+promises.push(getUrlContent(url1))
+promises.push(getUrlContent(url2))
+promises.push(getUrlContent(url3))
+
+Q.all(promises)
+  .then(function (content) {
+    // content[0] === content for url 1
+    // content[1] === content for url 2
+    // content[2] === content for url 3
+  })
+```
+
+If any of the promises fail, Q.all will fail as well (so make sure to guard your promises with a `.fail()` call beforehand if you don't care whether they succeed or not):
+
+```javascript
+var promises = []
+promises.push(getUrlContent(url1))
+promises.push(getUrlContent(url2))
+promises.push(getUrlContent(url3))
+
+Q.all(promises)
+  .fail(function (e) {
+    console.log("Failed retrieving a url", e)
+  })
+```
+
+### `.delay()` for future promises
+
+If you need a little bit of delay (such as retrying a method call to a service that is "eventually consistent") before doing something else, ``Q.delay()`` is your friend:
+
+```javascript
+getUrlContent(url1)
+.fail(function () {
+  // Retry again after 200 milisseconds
+  return Q.delay(200).then(function () {
+    return getUrlContent(url1)
+  })
+})
+```
+
+If two arguments are passed, the first will be used as the return value, and the
+second will be the delay in milliseconds.
+
+```javascript
+Q.delay(obj, 20).then(function (result) {
+  console.log(result) // logs `obj` after 20ms
+})
+```
+
+### `.fcall()` for delaying a function invocation until the next tick:
+```javascript
+// Assume someFn() is a synchronous 2 argument function you want to delay.
+Q.fcall(someFn, arg1, arg2)
+  .then(function (result) {
+    console.log('someFn(' + arg1 + ', ' + arg2 + ') = ' + result)
+  })
+```
+
+You can also use ``Q.fcall()`` with functions that return promises.
+
+### `.ncall()` and `.nfcall()` for Node.js callbacks
+
+``Q.nfcall()`` can be used to convert node-style callbacks into promises:
+
+```javascript
+Q.nfcall(fs.writeFile, '/tmp/myFile', 'content')
+  .then(function () {
+    console.log('File written successfully')
+  })
+  .fail(function (err) {
+    console.log('Failed to write file', err)
+  })
+```
+
+If your Node-style callback needs a `this` context, you can use `Q.ncall`:
+
+```js
+Q.ncall(redis.del, redis, 'my-key')
+  .then(function () { return true })
+  .fail(function () { return false })
+```
+
+
+### `.spread()` for arrays of promises
+
+``()`` can be used to convert node-style callbacks into promises:
+
+```javascript
+Q.nfcall(function () {
+  return ['a', Q.resolve('b')]
+})
+.spread(function (a, b) { 
+  // ...
+})
+```
+
+
+Contributing
+------------
+
+Questions, comments, bug reports, and pull requests are all welcome.
+Submit them at [the project on GitHub](https://github.com/Obvious/kew/).
+
+Bug reports that include steps-to-reproduce (including code) are the
+best. Even better, make them in the form of pull requests that update
+the test suite. Thanks!
+
+
+Author
+------
+
+[Jeremy Stanley](https://github.com/azulus)
+supported by
+[The Obvious Corporation](http://obvious.com/).
+
+
+License
+-------
+
+Copyright 2013 [The Obvious Corporation](http://obvious.com/).
+
+Licensed under the Apache License, Version 2.0.
+See the top-level file `LICENSE.TXT` and
+(http://www.apache.org/licenses/LICENSE-2.0).