chore(deps): bump read-excel-file from 8.0.3 to 9.0.6 in /js

[dependabot]

Bumps read-excel-file from 8.0.3 to 9.0.6.

Changelog

Sourced from read-excel-file's changelog.

9.0.0 / 18.04.2026

• If you were using parseData() function:
  • Rewrote the code of the parseData() function and renamed it to parseSheetData().
  • The result of parseSheetData() 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 parseSheetData() 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. It's the number of the data row that caused the error, starting from 1.
    • Added columnIndex: number property to the error object.
  • Renamed some of the exported TypeScript types:
    • ParseDataCustomType → ParseSheetDataCustomType
    • ParseDataCustomTypeErrorMessage → ParseSheetDataCustomTypeErrorMessage
    • ParseDataCustomTypeErrorReason → ParseSheetDataCustomTypeErrorReason
    • ParseDataError → ParseSheetDataError
    • ParseDataValueRequiredError → ParseSheetDataValueRequiredError
    • ParseDataResult → ParseSheetDataResult
  • 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

• 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.

... (truncated)

Commits

• 03527a5 9.0.6
• 6ca0745 README: error.columnIndex
• dcfa9f3 9.0.5
• 7149182 Added columnIndex: number property to the error object
• 1fac3b5 9.0.4
• 2427b3a Renamed parseData() to parseSheetData()
• 7a84671 9.0.3
• a94c6d0 Rewrote migration notes and readme parts
• ec7a807 9.0.2
• ccadede Fixed parseData() return type in readme
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.