read-excel-file 9.0.2 → 9.0.3

package/CHANGELOG.md

@@ -1,51 +1,67 @@
 9.0.0 / 18.04.2026
 ==================
 
-* Refactored `parseData()` function.
-* The result of `parseData()` function is now `{ errors, objects }`. If there're no errors, `errors` will be `undefined`. Otherwise, `errors` will be a non-empty array and `objects` will be `undefined`.
-  * Previously the result of `parseData()` function was `[{ errors, object }, ...]`, i.e. the `errors` were split between each particular data row. Now the `errors` are combined for all data rows. The rationale is that it's simpler to handle the result of the function this way.
-  * Re-added `row: number` property to the `error` object.
-* In a schema, a nested object is now not allowed to be `required: true`. Otherwise, if a nested object was allowed to be `required: true`, a corresponding `"required"` error  would have to include a specific `column` title but a nested object simply doesn't have one.
+* If you were using `parseData()` function:
+  * Rewrote the code of the `parseData()` function.
+  * The result of `parseData()` function is now `{ errors, objects }`. If there're no errors, `errors` will be `undefined`. Otherwise, `errors` will be a non-empty array and `objects` will be `undefined`.
+    * Previously the result of `parseData()` function was `[{ errors, object }, ...]`, i.e. the `errors` were split between each particular data row. Now the `errors` are combined for all data rows. The rationale is that it's simpler to handle the result of the function this way.
+    * Re-added `row: number` property to the `error` object.
+  * In a `schema`, a nested object could be declared as: `{ required: true/false, schema: { ... } }`. This is still true but the `required` flag is now only allowed to be either `undefined` or `false`, so `true` value is not allowed. The reason is quite simple. If a nested object as a whole is marked as `required: true`, and then it happens to be empty, a `"required"` error should be returned for it. But that error would also have to include a `column` title, and a nested object simply can't be pinned down to a single column in a sheet because it is by definition spread over multiple columns. So instead of marking a nested object as a whole with `required: true`, mark the specific required properties of it.
 
 8.0.0 / 11.03.2026
 ==================
 
-* Renamed the default exported function to a named exported function `readSheet`.
-  * Old: `import readExcelFile from "read-excel-file/browser"`
-  * New: `import { readSheet } from "read-excel-file/browser"`
-  * And same for other exports like `"read-excel-file/node"`, etc.
-* The default exported function now returns all sheets in a form of an array of objects: `[{ name: "Sheet 1", rows: [['a','b','c'],['d','e','f']] }, ...]`.
-* Removed `getSheets: true` parameter. The default exported function now returns all sheets.
-* Removed exported `readSheetNames()` function. The default exported function now returns all sheets.
-* Removed `schema` parameter. Instead, use exported function `parseData(data, schema)` to map data to an array of objects.
-  * Old: `import readExcelFile from "read-excel-file"` and then `const { rows, errors } = await readExcelFile(..., { schema })`
-  * New: `import { readSheet, parseData } from "read-excel-file/browser"` and then `const result = parseData(await readSheet(...), schema)`
-    * The `result` of the function is an array where each element represents a "data row" and has shape `{ object, errors }`.
-      * Depending on whether there were any errors when parsing a given "data row", either `object` or `errors` property will be `undefined`.
-      * The `errors` don't have a `row` property anymore because it could be derived from "data row" number.
-        * In version `9.x`, the `row` property has been re-added, so consider migrating straight to `9.x`.
-      * In version `9.x`, the returned result of `parseData()` has been changed back to `{ errors, objects }`, so consider migrating straight to `9.x`. In that case, if there're no errors, `errors` will be `undefined`; otherwise, `errors` will be a non-empty array and `objects` will be `undefined`.
-* Removed `transformData` parameter because `schema` parameter was removed. A developer could transform the `data` themself and then pass it to `parseData()` function.
-* Removed `isColumnOriented` parameter.
-* Removed `ignoreEmptyRows` parameter. Empty rows somewhere in the middle are not ignored now.
-* Renamed some options that're used when parsing using a `schema`:
-	* `schemaPropertyValueForMissingColumn` → `propertyValueWhenColumnIsMissing`
-	* `schemaPropertyValueForMissingValue` → `propertyValueWhenCellIsEmpty`
-	* `schemaPropertyShouldSkipRequiredValidationForMissingColumn` → (removed)
-	* `getEmptyObjectValue` → `transformEmptyObject`
-    * The leading `.` character is now removed from the `path` parameter.
-	* `getEmptyArrayValue` → `transformEmptyArray`
-    * The leading `.` character is now removed from the `path` parameter.
-* Previously, when parsing comma-separated values, it used to ignore any commas that're surrounded by quotes, similar to how it's done in `.csv` files. Now it no longer does that.
-* Previously, when parsing comma-separated values, it used to allow empty-string elements. Now it no longer does that and such empty-string elements will now result in an error with properties: `{ error: "invalid", reason: "syntax" }`.
-* Previously, when parsing using a schema, it used to force-convert all `type: Date` schema properties from any numeric cell value to a `Date` with a given timestamp. Now it demands the cell values for all such `type: Date` schema properties to already be correctly recognized as `Date`s when they're returned from `readSheet()` or `readExcelFile()` function. And I'd personally assume that in any sane (non-contrived) real-world usage scenario that would be the case, so it doesn't really seem like a "breaking change". And if, for some strange reason, that happens not to be the case, `parseData()` function will throw an error: `not_a_date`.
-* Previously, when parsing using a schema, it used to skip `required` validation for completely-empty rows. It no longer does that.
-* Removed exported function `parseExcelDate()` because there seems to be no need to have it exported.
-* (TypeScript) Renamed exported types:
-  * `Type` → `ParseDataCustomType`
-  * `Error` or `SchemaParseCellValueError` → `ParseDataError`
-  * `CellValueRequiredError` → `ParseDataValueRequiredError`
-  * `ParsedObjectsResult` → `ParseDataResult`
+* If you were using the default exported function:
+  * Renamed the default exported function to a named exported function `readSheet`.
+    * Old: `import readExcelFile from "read-excel-file/browser"`
+    * New: `import { readSheet } from "read-excel-file/browser"`
+    * And same for other exports like `"read-excel-file/node"`, etc.
+  * The default exported function now returns a different kind of result. Specifically, now it returns all available sheets — an array of objects: `[{ sheet: "Sheet 1", data: [['a1','b1','c1'],['a2','b2','c2']] }, ...]`.
+  * The default exported function used to return sheet names when passed `getSheets: true` parameter. Now, instead of that, the default exported function just returns all available sheets, from which one could get the sheet names.
+
+* If you were using `readSheetNames()` function:
+  * Removed exported function `readSheetNames()`. Use the default exported function instead. The default exported function now returns all sheets.
+
+* If you were using `parseExcelDate()` function:
+  * Removed exported function `parseExcelDate()` because there seems to be no need to have it exported.
+
+* If you were using `schema` parameter:
+  * Removed `schema` parameter. Instead, use exported function `parseData(data, schema)` to map data to an array of objects.
+    * Old: `import readXlsxFile from "read-excel-file"` and then `const { rows, errors } = await readXlsxFile(..., { schema })`
+    * New: `import { readSheet, parseData } from "read-excel-file/browser"` and then `const result = parseData(await readSheet(...), schema)`
+      * The `result` of the function is an array where each element represents a "data row" and has shape `{ object, errors }`.
+        * Depending on whether there were any errors when parsing a given "data row", either `object` or `errors` property will be `undefined`.
+        * The `errors` don't have a `row` property anymore because it could be derived from "data row" number.
+          * In version `9.x`, the `row` property has been re-added, so consider migrating straight to `9.x`.
+        * In version `9.x`, the returned result of `parseData()` has been changed back to `{ errors, objects }`, so consider migrating straight to `9.x`. In that case, if there're no errors, `errors` will be `undefined`; otherwise, `errors` will be a non-empty array and `objects` will be `undefined`.
+  * Renamed some `schema`-related parameters:
+    * `schemaPropertyValueForMissingColumn` → `propertyValueWhenColumnIsMissing`
+    * `schemaPropertyValueForMissingValue` → `propertyValueWhenCellIsEmpty`
+    * `schemaPropertyShouldSkipRequiredValidationForMissingColumn` → (removed)
+    * `getEmptyObjectValue` → `transformEmptyObject`
+      * The leading `.` character is now removed from the `path` parameter.
+    * `getEmptyArrayValue` → `transformEmptyArray`
+      * The leading `.` character is now removed from the `path` parameter.
+  * Previously, when using a `schema` to parse comma-separated values, it used to ignore any commas that're surrounded by quotes, similar to how it's done in `.csv` files. Now it no longer does that.
+  * Previously, when using a `schema` to parse comma-separated values, it used to allow empty-string elements. Now it no longer does that and such empty-string elements will now result in an error with properties: `{ error: "invalid", reason: "syntax" }`.
+  * Previously, when using a `schema` to parse `type: Date` properties, it used to support both `Date` objects and numeric timestamps as the input data for the property value. In the latter case, it simply force-converted those numeric timestamps to corresponding `Date` objects. Now `parseData()` function no longer does that, and demands the input data for `type: Date` schema properties to only be `Date` objects, i.e. it shifts the responsibility to interpret date cell values correctly onto `readSheet()` and `readExcelFile()` functions. And I'd personally assume that in any real-world (i.e. non-contrived) scenario those functions would interpret date cell values correctly, so I personally don't consider this a "breaking change". Still, formally, it is a "breaking change" and therefore should be mentioned. So if, for some strange reason, those two functions happen to not recognize a date cell value correctly, `parseData()` function will return an error for such cell: `"not_a_date"`.
+  * Previously, when using a `schema` to parse sheet data, and a given row of data was completely empty, it didn't run any `required` property validations. Now it no longer does that and it will run all `required` property validations regardless of whether it's a completely empty row of data or not.
+
+* If you were using `transformData` parameter:
+  * Removed `transformData` parameter because the `schema` parameter was extracted into a separate function called `parseData()`. Now, if required, a developer could transform the `data` manually and then pass it to `parseData()` function.
+
+* If you were using `isColumnOriented` parameter:
+  * Removed `isColumnOriented` parameter because it seemed to be of no use.
+
+* If you were using `ignoreEmptyRows` parameter:
+  * Removed `ignoreEmptyRows` parameter. Empty rows somewhere in the middle of a sheet are not ignored now. That doesn't concern empty rows at the end of a sheet though — those're still ignored.
+
+* If you were using TypeScript:
+  * Renamed some of the exported types:
+    * `Type` → `ParseDataCustomType`
+    * `Error` or `SchemaParseCellValueError` → `ParseDataError`
+    * `CellValueRequiredError` → `ParseDataValueRequiredError`
+    * `ParsedObjectsResult` → `ParseDataResult`
 
 7.0.1 / 04.03.2026
 ==================

package/README.md

@@ -24,42 +24,57 @@ Also check out [`write-excel-file`](https://www.npmjs.com/package/write-excel-fi
 
 ######
 
-* Renamed the default exported function to a named exported function `readSheet`.
-  * Old: `import readExcelFile from "read-excel-file/browser"`
-  * New: `import { readSheet } from "read-excel-file/browser"`
-  * And same for other exports like `"read-excel-file/node"`, etc.
-* The default exported function now returns all sheets in a form of an array of objects: `[{ sheet: "Sheet 1", data: [['a1','b1','c1'],['a2','b2','c2']] }, ...]`.
-* Removed `getSheets: true` parameter. The default exported function now returns all sheets.
-* Removed exported `readSheetNames()` function. The default exported function now returns all sheets.
-* Removed `schema` parameter. Instead, use exported function `parseData(data, schema)` to map data to an array of objects.
-  * Old: `import readXlsxFile from "read-excel-file"` and then `const { rows, errors } = await readXlsxFile(..., { schema })`
-  * New: `import { readSheet, parseData } from "read-excel-file/browser"` and then `const result = parseData(await readSheet(...), schema)`
-    * The `result` of the function is an array where each element represents a "data row" and has shape `{ object, errors }`.
-      * Depending on whether there were any errors when parsing a given "data row", either `object` or `errors` property will be `undefined`.
-      * The `errors` don't have a `row` property anymore because it could be derived from "data row" number.
-        * In version `9.x`, the `row` property has been re-added, so consider migrating straight to `9.x`.
-      * In version `9.x`, the returned result of `parseData()` has been changed back to `{ errors, objects }`, so consider migrating straight to `9.x`. In that case, if there're no errors, `errors` will be `undefined`; otherwise, `errors` will be a non-empty array and `objects` will be `undefined`.
-* Removed `transformData` parameter because `schema` parameter was removed. A developer could transform the `data` themself and then pass it to `parseData()` function.
-* Removed `isColumnOriented` parameter.
-* Removed `ignoreEmptyRows` parameter. Empty rows somewhere in the middle are not ignored now.
-* Renamed some options that're used when parsing using a `schema`:
-	* `schemaPropertyValueForMissingColumn` → `propertyValueWhenColumnIsMissing`
-	* `schemaPropertyValueForMissingValue` → `propertyValueWhenCellIsEmpty`
-	* `schemaPropertyShouldSkipRequiredValidationForMissingColumn` → (removed)
-	* `getEmptyObjectValue` → `transformEmptyObject`
-    * The leading `.` character is now removed from the `path` parameter.
-	* `getEmptyArrayValue` → `transformEmptyArray`
-    * The leading `.` character is now removed from the `path` parameter.
-* Previously, when parsing comma-separated values, it used to ignore any commas that're surrounded by quotes, similar to how it's done in `.csv` files. Now it no longer does that.
-* Previously, when parsing comma-separated values, it used to allow empty-string elements. Now it no longer does that and such empty-string elements will now result in an error with properties: `{ error: "invalid", reason: "syntax" }`.
-* Previously, when parsing using a schema, it used to force-convert all `type: Date` schema properties from any numeric cell value to a `Date` with a given timestamp. Now it demands the cell values for all such `type: Date` schema properties to already be correctly recognized as `Date`s when they're returned from `readSheet()` or `readExcelFile()` function. And I'd personally assume that in any sane (non-contrived) real-world usage scenario that would be the case, so it doesn't really seem like a "breaking change". And if, for some strange reason, that happens not to be the case, `parseData()` function will throw an error: `not_a_date`.
-* Previously, when parsing using a schema, it used to skip `required` validation for completely-empty rows. It no longer does that.
-* Removed exported function `parseExcelDate()` because there seems to be no need to have it exported.
-* (TypeScript) Renamed exported types:
-  * `Type` → `ParseDataCustomType`
-  * `Error` or `SchemaParseCellValueError` → `ParseDataError`
-  * `CellValueRequiredError` → `ParseDataValueRequiredError`
-  * `ParsedObjectsResult` → `ParseDataResult`
+* If you were using the default exported function:
+  * Renamed the default exported function to a named exported function `readSheet`.
+    * Old: `import readExcelFile from "read-excel-file/browser"`
+    * New: `import { readSheet } from "read-excel-file/browser"`
+    * And same for other exports like `"read-excel-file/node"`, etc.
+  * The default exported function now returns a different kind of result. Specifically, now it returns all available sheets — an array of objects: `[{ sheet: "Sheet 1", data: [['a1','b1','c1'],['a2','b2','c2']] }, ...]`.
+  * The default exported function used to return sheet names when passed `getSheets: true` parameter. Now, instead of that, the default exported function just returns all available sheets, from which one could get the sheet names.
+
+* If you were using `readSheetNames()` function:
+  * Removed exported function `readSheetNames()`. Use the default exported function instead. The default exported function now returns all sheets.
+
+* If you were using `parseExcelDate()` function:
+  * Removed exported function `parseExcelDate()` because there seems to be no need to have it exported.
+
+* If you were using `schema` parameter:
+  * Removed `schema` parameter. Instead, use exported function `parseData(data, schema)` to map data to an array of objects.
+    * Old: `import readXlsxFile from "read-excel-file"` and then `const { rows, errors } = await readXlsxFile(..., { schema })`
+    * New: `import { readSheet, parseData } from "read-excel-file/browser"` and then `const result = parseData(await readSheet(...), schema)`
+      * The `result` of the function is an array where each element represents a "data row" and has shape `{ object, errors }`.
+        * Depending on whether there were any errors when parsing a given "data row", either `object` or `errors` property will be `undefined`.
+        * The `errors` don't have a `row` property anymore because it could be derived from "data row" number.
+          * In version `9.x`, the `row` property has been re-added, so consider migrating straight to `9.x`.
+        * In version `9.x`, the returned result of `parseData()` has been changed back to `{ errors, objects }`, so consider migrating straight to `9.x`. In that case, if there're no errors, `errors` will be `undefined`; otherwise, `errors` will be a non-empty array and `objects` will be `undefined`.
+  * Renamed some `schema`-related parameters:
+    * `schemaPropertyValueForMissingColumn` → `propertyValueWhenColumnIsMissing`
+    * `schemaPropertyValueForMissingValue` → `propertyValueWhenCellIsEmpty`
+    * `schemaPropertyShouldSkipRequiredValidationForMissingColumn` → (removed)
+    * `getEmptyObjectValue` → `transformEmptyObject`
+      * The leading `.` character is now removed from the `path` parameter.
+    * `getEmptyArrayValue` → `transformEmptyArray`
+      * The leading `.` character is now removed from the `path` parameter.
+  * Previously, when using a `schema` to parse comma-separated values, it used to ignore any commas that're surrounded by quotes, similar to how it's done in `.csv` files. Now it no longer does that.
+  * Previously, when using a `schema` to parse comma-separated values, it used to allow empty-string elements. Now it no longer does that and such empty-string elements will now result in an error with properties: `{ error: "invalid", reason: "syntax" }`.
+  * Previously, when using a `schema` to parse `type: Date` properties, it used to support both `Date` objects and numeric timestamps as the input data for the property value. In the latter case, it simply force-converted those numeric timestamps to corresponding `Date` objects. Now `parseData()` function no longer does that, and demands the input data for `type: Date` schema properties to only be `Date` objects, i.e. it shifts the responsibility to interpret date cell values correctly onto `readSheet()` and `readExcelFile()` functions. And I'd personally assume that in any real-world (i.e. non-contrived) scenario those functions would interpret date cell values correctly, so I personally don't consider this a "breaking change". Still, formally, it is a "breaking change" and therefore should be mentioned. So if, for some strange reason, those two functions happen to not recognize a date cell value correctly, `parseData()` function will return an error for such cell: `"not_a_date"`.
+  * Previously, when using a `schema` to parse sheet data, and a given row of data was completely empty, it didn't run any `required` property validations. Now it no longer does that and it will run all `required` property validations regardless of whether it's a completely empty row of data or not.
+
+* If you were using `transformData` parameter:
+  * Removed `transformData` parameter because the `schema` parameter was extracted into a separate function called `parseData()`. Now, if required, a developer could transform the `data` manually and then pass it to `parseData()` function.
+
+* If you were using `isColumnOriented` parameter:
+  * Removed `isColumnOriented` parameter because it seemed to be of no use.
+
+* If you were using `ignoreEmptyRows` parameter:
+  * Removed `ignoreEmptyRows` parameter. Empty rows somewhere in the middle of a sheet are not ignored now. That doesn't concern empty rows at the end of a sheet though — those're still ignored.
+
+* If you were using TypeScript:
+  * Renamed some of the exported types:
+    * `Type` → `ParseDataCustomType`
+    * `Error` or `SchemaParseCellValueError` → `ParseDataError`
+    * `CellValueRequiredError` → `ParseDataValueRequiredError`
+    * `ParsedObjectsResult` → `ParseDataResult`
 </details>
 
 <details>
@@ -67,11 +82,12 @@ Also check out [`write-excel-file`](https://www.npmjs.com/package/write-excel-fi
 
 ######
 
-* Refactored `parseData()` function.
-* The result of `parseData()` function is now `{ errors, objects }`. If there're no errors, `errors` will be `undefined`. Otherwise, `errors` will be a non-empty array and `objects` will be `undefined`.
-  * Previously the result of `parseData()` function was `[{ errors, object }, ...]`, i.e. the `errors` were split between each particular data row. Now the `errors` are combined for all data rows. The rationale is that it's simpler to handle the result of the function this way.
-  * Re-added `row: number` property to the `error` object.
-* In a schema, a nested object is now not allowed to be `required: true`. Otherwise, if a nested object was allowed to be `required: true`, a corresponding `"required"` error  would have to include a specific `column` title but a nested object simply doesn't have one.
+* If you were using `parseData()` function:
+  * Rewrote the code of the `parseData()` function.
+  * The result of `parseData()` function is now `{ errors, objects }`. If there're no errors, `errors` will be `undefined`. Otherwise, `errors` will be a non-empty array and `objects` will be `undefined`.
+    * Previously the result of `parseData()` function was `[{ errors, object }, ...]`, i.e. the `errors` were split between each particular data row. Now the `errors` are combined for all data rows. The rationale is that it's simpler to handle the result of the function this way.
+    * Re-added `row: number` property to the `error` object.
+  * In a `schema`, a nested object could be declared as: `{ required: true/false, schema: { ... } }`. This is still true but the `required` flag is now only allowed to be either `undefined` or `false`, so `true` value is not allowed. The reason is quite simple. If a nested object as a whole is marked as `required: true`, and then it happens to be empty, a `"required"` error should be returned for it. But that error would also have to include a `column` title, and a nested object simply can't be pinned down to a single column in a sheet because it is by definition spread over multiple columns. So instead of marking a nested object as a whole with `required: true`, mark the specific required properties of it.
 </details>
 
 ## Install
@@ -84,19 +100,21 @@ Alternatively, it could be included on a web page [directly](#cdn) via a `<scrip
 
 ## Use
 
-If your `.xlsx` file only has a single "sheet", or if you only care for a single "sheet", or if you don't know or care what a "sheet" is, use `readSheet()` function.
+If your `.xlsx` file only has a single "sheet", or if you only need to read a single "sheet", or if you don't care what a "sheet" is, use `readSheet()` function.
+
+For example, consider the following `.xlsx` file:
 
 | Name       | Date of Birth | Married | Kids |
 | ---------- | ------------- | ------- | ---- |
 | John Smith | 1/1/1995      | TRUE    | 3    |
 | Kate Brown | 3/1/2010      | FALSE   | 0    |
 
+Here's how to read it using `readSheet()` function:
+
 ```js
 import { readSheet } from 'read-excel-file/node'
 
-await readSheet(file)
-
-// Returns
+await readSheet(file) ===
 [
   ['Name', 'Date of Birth', 'Married', 'Kids'],
   ['John Smith', 1995-01-01T00:00:00.000Z, true, 3],
@@ -104,20 +122,18 @@ await readSheet(file)
 ]
 ```
 
-It resolves to an array of rows. Each row is an array of values — `string`, `number`, `boolean` or `Date`.
+The result is an array of rows. Each row is an array of values — `string`, `number`, `boolean` or `Date`.
 
 <!-- It's same as the default exported function shown above with the only difference that it returns just `data` instead of `[{ name: 'Sheet1', data }]`, so it's just a bit simpler to use. It has an optional second argument — `sheet` — which could be a sheet number (starting from `1`) or a sheet name. By default, it reads the first sheet. -->
 
-And it has an optional second argument — `sheet` — which could be a sheet number (starting from `1`) or a sheet name. By default, it reads the first sheet.
+It also has an optional second argument — `sheet` — which could be a sheet number (starting from `1`) or a sheet name. By default, it reads the first sheet.
 
-But if you need to read all "sheets" for some reason, use the default exported function which resolves to an array of "sheets".
+But if you need to read all available "sheets" in a file, use the default exported function:
 
 ```js
 import readExcelFile from 'read-excel-file/node'
 
-await readExcelFile(file)
-
-// Returns
+await readExcelFile(file) ===
 [{
   sheet: 'Sheet1',
   data: [
@@ -131,19 +147,21 @@ await readExcelFile(file)
 }]
 ```
 
-At least one "sheet" always exists. Each "sheet" is an object with properties:
+The result is a non-empty array of "sheets". Each "sheet" is an object with properties:
 * `sheet` — Sheet name.
   * Example: `"Sheet1"`
 * `data` — Sheet data. An array of rows. Each row is an array of values — `string`, `number`, `boolean` or `Date`.
   * Example: `[ ['Name','Age'], ['John Smith',30], ['Kate Brown',15] ]`
 
-## API
+## Import
 
 This package provides a separate `import` path for each different environment, as described below.
 
 ### Browser
 
-It can read a [`File`](https://developer.mozilla.org/en-US/docs/Web/API/File), a [`Blob`](https://developer.mozilla.org/en-US/docs/Web/API/Blob) or an [`ArrayBuffer`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer).
+`read-excel-file/browser`
+
+It can read from a [`File`](https://developer.mozilla.org/en-US/docs/Web/API/File), a [`Blob`](https://developer.mozilla.org/en-US/docs/Web/API/Blob) or an [`ArrayBuffer`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer).
 
 Example: User chooses a file and the web application reads it.
 
@@ -180,7 +198,7 @@ const data = await readSheet(blob)
 
 ######
 
-All exports of `read-excel-file` already use a [Web Worker](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers) under the hood when reading `.xlsx` file contents. This is in order to avoid freezing the UI when reading large files. So using an additional Web Worker on top of that isn't really necessary. Still, for those who require it, this example shows how a user chooses a file and the web application reads it in a [Web Worker](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers).
+All exports of `read-excel-file` already use a [Web Worker](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers) under the hood when reading `.xlsx` file contents. This is in order to avoid freezing the UI when reading large files. So using an additional Web Worker on top of that isn't really necessary. Still, for those who require it, this example shows how a user chooses a file and the web application reads it in a [Web Worker](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers) using `read-excel-file/web-worker` import path.
 
 ```js
 // Step 1: Initialize Web Worker.
@@ -219,7 +237,9 @@ onmessage = async function(event) {
 
 ### Node.js
 
-It can read a file path, a [`Stream`](https://nodejs.org/api/stream.html), a [`Buffer`](https://nodejs.org/api/buffer.html) or a [`Blob`](https://developer.mozilla.org/docs/Web/API/Blob).
+`read-excel-file/node`
+
+It can read from a file path, a [`Stream`](https://nodejs.org/api/stream.html), a [`Buffer`](https://nodejs.org/api/buffer.html) or a [`Blob`](https://developer.mozilla.org/docs/Web/API/Blob).
 
 Example 1: Read from a file path.
 
@@ -239,6 +259,8 @@ const data = await readSheet(fs.createReadStream('/path/to/file'))
 
 ### Universal
 
+`read-excel-file/universal`
+
 This one works both in a web browser and Node.js. It can only read from a [`Blob`](https://developer.mozilla.org/en-US/docs/Web/API/Blob) or an [`ArrayBuffer`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer), which could be a bit less convenient for general use.
 
 ```js

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "read-excel-file",
-  "version": "9.0.2",
+  "version": "9.0.3",
   "description": "Read `.xlsx` files in a web browser or in Node.js",
   "type": "module",
   "exports": {