chore(deps): Bump read-excel-file from 7.0.3 to 8.0.3 in /js

[dependabot]

Bumps read-excel-file from 7.0.3 to 8.0.3.

Changelog

Sourced from read-excel-file's changelog.

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

7.0.1 / 04.03.2026

• Fixed CellValue TypeScript type (it didn't include null value).

• (TypeScript minor breaking change) Renamed exported Error TypeScript interface to SchemaParseCellValueError, and removed CellValue generic from it.

7.0.0 / 23.02.2026

• Refactored the code.
• (breaking change) The minimum required Node.js version is now >= 18.

... (truncated)

Commits

• fb8613e 8.0.3
• f6ddacd Edited readme
• e296cf5 Finished fixing parseData() custom type typescript
• a3b9c2d Readme don't show table
• c5f5d96 Out-of-place commas in array types now cause an error
• c4de75d Out-of-place commas in array types now cause an error
• 383de89 8.0.2
• 32ac67f Simplified "Use" section
• 978b5bc Demo: fixed line-height in virtual scroller
• 1b2fe3e 8.0.1
• 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.