Comparing version 0.1.4 to 1.0.0
11
index.js
@@ -1,7 +0,1 @@ | ||
exports.reader = require("./lib/rw/reader"); | ||
exports.writer = require("./lib/rw/writer"); | ||
exports.fileReader = require("./lib/rw/file-reader"); | ||
exports.fileWriter = require("./lib/rw/file-writer"); | ||
exports.readFile = require("./lib/rw/read-file"); | ||
@@ -11,6 +5,1 @@ exports.readFileSync = require("./lib/rw/read-file-sync"); | ||
exports.writeFileSync = require("./lib/rw/write-file-sync"); | ||
exports.lineParser = require("./lib/rw/line-parser"); | ||
exports.dsvParser = require("./lib/rw/dsv-parser"); | ||
exports.pipe = require("./lib/rw/pipe"); |
{ | ||
"name": "rw", | ||
"version": "0.1.4", | ||
"description": "Wrappers of fs.{read,write}File that work for /dev/std{in,out}.", | ||
"version": "1.0.0", | ||
"description": "Now stdin and stdout are files.", | ||
"keywords": [ | ||
@@ -12,3 +12,4 @@ "fs", | ||
], | ||
"main": "index.js", | ||
"homepage": "https://github.com/mbostock/rw", | ||
"license": "BSD-3-Clause", | ||
"author": { | ||
@@ -18,6 +19,10 @@ "name": "Mike Bostock", | ||
}, | ||
"main": "index.js", | ||
"repository": { | ||
"type": "git", | ||
"url": "http://github.com/mbostock/rw.git" | ||
}, | ||
"scripts": { | ||
"test": "test/run-tests && eslint index.js lib" | ||
} | ||
} |
@@ -1,2 +0,2 @@ | ||
# stdin & stdout, the right way | ||
# rw - Now stdin and stdout are files. | ||
@@ -62,4 +62,2 @@ How do you read a file from stdin? If you thought, | ||
## rw | ||
The **rw** module fixes these problems. It provides an interface just like readFile, readFileSync, writeFile and writeFileSync, but with implementations that work the way you expect on stdin and stdout. If you use these methods on files other than /dev/stdin or /dev/stdout, they simply delegate to the fs methods, so you can trust that they behave identically to the methods you’re used to. | ||
@@ -66,0 +64,0 @@ |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
No tests
QualityPackage does not have any tests. This is a strong signal of a poorly maintained or low quality package.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
0
4
13541
16
116
79
1