| function functionThatMightThrow(input) | |
| { | |
| return JSON.parse(input); | |
| } | |
| function putTogetherSomeData(input, callback) | |
| { | |
| var result = {}; | |
| redis.get(input, function(err, reply) |
Go here for the latest + some code.
An alerting engine for a metrics & monitoring system.
This is the same approach I wanted in my initial spike, only instead of writing a custom collector & using an existing alerting engine (riemann), I'm proposing using an existing collector (hekad) and writing the alerting engine.
| team-cave-newt:master* λ node camera.js | |
| 640 | |
| 368 | |
| 7.982560051722453e+83 | |
| 640 | |
| 368 | |
| 2.516806656184071e+253 | |
| 640 | |
| 368 | |
| 2.529804685642898e+79 |
| $ touch -t 196508231405.14 ./test.tgz" | |
| $ stat ./test.tgz | |
| File: ‘test.tgz’ | |
| Size: 6012 Blocks: 16 IO Block: 4096 regular file | |
| Device: 900h/2304d Inode: 127402426 Links: 1 | |
| Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) | |
| Access: 1965-08-23 14:05:14.000000000 +0000 | |
| Modify: 1965-08-23 14:05:14.000000000 +0000 | |
| Change: 2016-07-06 17:35:26.871223783 +0000 |
| 2001 silly decomposeActions build combined-stream@1.0.5 | |
| 2002 silly decomposeActions install combined-stream@1.0.5 | |
| 2003 silly decomposeActions postinstall combined-stream@1.0.5 | |
| 2004 silly decomposeActions finalize combined-stream@1.0.5 | |
| 2005 silly decomposeActions refresh-package-json combined-stream@1.0.5 | |
| 2006 silly decomposeActions fetch commander@2.9.0 | |
| 2007 silly decomposeActions extract commander@2.9.0 | |
| 2008 silly decomposeActions preinstall commander@2.9.0 | |
| 2009 silly decomposeActions build commander@2.9.0 | |
| 2010 silly decomposeActions install commander@2.9.0 |
Alice is writing a new library, and she is excited to use the new ES6 syntax. However, she would like to use an older but still good package she found on npm, that exports its interface using CommonJS. She does so easily after reading the NodeJS documentation on how to do this.
Bob is updating a module for his work, and he needs to support existing CommonJS-using codebases as well as a new project that prefers to stick with ES6 for static analysis reasons. He publishes a package that exports both kinds of interfaces.
Carol is updating her popular code coverage reporting tool for the new world. She uses the ESM loader hooks to instrument test code as it is imported so she can get code coverage reporting on par with what she has for CommonJS.
David is writing a transpiler. He writes a custom hook that transpiles source as it's loaded from his language to JavaScript.
See this Cloudup stream for visual references.
The short answer is that I miss everything. There is no comparing the two projects. Stash's feature set is a shadow of Github's.
What a project looks like on Github:
| [ | |
| { | |
| "name": "Vurts Ascadian Isles Trees Replacer II", | |
| "game": "morrowind", | |
| "modId": 37249, | |
| "fileId": 76153 | |
| }, | |
| { | |
| "name": "HQ Weapons", | |
| "game": "morrowind", |
