Comparing version 1.0.2 to 1.1.0
{ | ||
"name": "debussy", | ||
"version": "1.0.2", | ||
"version": "1.1.0", | ||
"description": "simple, fast, and efficient file reader, line by line", | ||
@@ -11,3 +11,3 @@ "main": "index.js", | ||
"type": "git", | ||
"url": "git@github.com/gold/debussy.git" | ||
"url": "https://github.com/gold/debussy.git" | ||
}, | ||
@@ -18,3 +18,8 @@ "keywords": [ | ||
"file", | ||
"read file", | ||
"file reader", | ||
"line-by-line", | ||
"read line", | ||
"line", | ||
"stream reader", | ||
"reader", | ||
@@ -21,0 +26,0 @@ "stream" |
@@ -50,7 +50,9 @@ debussy | ||
Why `debussy`? After researching similar npm modules, I discovered I really | ||
didn't have to write this at all and I could be using someone else's npm package | ||
instead. But that's no fun. And naming the module to indicate its functionality | ||
would have thrown my version into a sea of names like file-reader, line-read, | ||
read-line, stream-line-reader, line-reader-stream, read-by-line, | ||
Why `debussy`? | ||
After researching similar npm modules, I discovered I really didn't have to | ||
write this at all and I could be using someone else's npm package instead. But | ||
that's no fun. And giving the module a name which represented its functionality | ||
would have lost my version in a sea of names like file-reader, line-read, | ||
file-line-read, stream-line-reader, line-reader-stream, read-by-line, | ||
reader-line-stuff, etc. | ||
@@ -57,0 +59,0 @@ |
4181
64