read-excel-file 6.0.0 → 6.0.1

package/README.md

@@ -4,8 +4,6 @@ Read `*.xlsx` files of moderate size in a web browser or on a server.
 
 It also supports parsing spreadsheet rows into JSON objects using a [schema](#schema).
 
-[Huge files](#performance) may not be supported.
-
 [Demo](https://catamphetamine.gitlab.io/read-excel-file/)
 
 Also check out [`write-excel-file`](https://www.npmjs.com/package/write-excel-file) for writing `*.xlsx` files.
@@ -216,7 +214,7 @@ Dynamically calculated cells using formulas (`SUM`, etc) are not supported.
 
 ## Performance
 
-There have been some [reports](https://github.com/catamphetamine/read-excel-file/issues/38#issuecomment-544286628) about performance issues when reading very large `*.xlsx` spreadsheets using this library. It's true that this library's main point have been usability and convenience, and not performance when handling huge datasets. For example, the time of parsing a file with 2000 rows and 20 columns could be more than 2 seconds. So for reading huge datasets, perhaps use something like [`xlsx`](https://github.com/catamphetamine/read-excel-file/issues/38#issuecomment-544286628) package instead. There're no comparative benchmarks between the two packages, so if you'll be making one, share it in the "Issues".
+There have been some reports about performance issues when reading extremely large `*.xlsx` spreadsheets using this library. It's true that this library's main point have been usability and convenience, and not performance when handling huge datasets. For example, the time of parsing a file with 100,000 rows could be up to 10 seconds. If your application has to quickly read huge datasets, perhaps consider using something like [`xlsx`](https://github.com/catamphetamine/read-excel-file/issues/38#issuecomment-544286628) package instead. There're no comparative benchmarks between the two packages, so we don't know how much the difference would be. If you'll be making any benchmarks, share those in the "Issues" so that we could include them in this readme.
 
 ## Schema
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "read-excel-file",
-  "version": "6.0.0",
+  "version": "6.0.1",
   "description": "Read `*.xlsx` files of moderate size in a web browser or on a server.",
   "module": "index.js",
   "main": "index.cjs",
@@ -29,7 +29,7 @@
     "test": "mocha --colors --bail --reporter spec --require ./test/setup.js \"./{,!(node_modules|commonjs|modules)/**/}*.test.js\" --recursive",
     "clean-for-build": "rimraf ./commonjs/**/* ./modules/**/*",
     "build-commonjs-modules": "better-npm-run build-commonjs-modules",
-    "build-commonjs-package.json": "node runnable/create-commonjs-package-json.js",
+    "build-commonjs-package.json": "node build-scripts/create-commonjs-package-json.js",
     "build-commonjs": "npm-run-all build-commonjs-modules build-commonjs-package.json",
     "build-es6-modules": "better-npm-run build-es6-modules",
     "browser-build": "rollup --config rollup.config.mjs",

package/runnable/create-commonjs-package-json.js

@@ -1,11 +0,0 @@
-// Creates a `package.json` file in the CommonJS `build` folder.
-// That marks that whole folder as CommonJS so that Node.js doesn't complain
-// about `require()`-ing those files.
-
-import fs from 'fs'
-
-fs.writeFileSync('./commonjs/package.json', JSON.stringify({
-	name: 'read-excel-file/commonjs',
-	type: 'commonjs',
-	private: true
-}, null, 2), 'utf8')