chore(deps): bump write-excel-file from 3.0.8 to 4.0.2 in /js

[dependabot]

Bumps write-excel-file from 3.0.8 to 4.0.2.

Changelog

Sourced from write-excel-file's changelog.

4.0.0 / 22.04.2026

• Changed the arguments of writeExcelFile() function.

  • The following options are now passed as part of a separate (third) argument: fontFamily, fontSize, features.

• Changed the arguments of writeExcelFile() function when writing a file with mulitiple sheets.

  • Old — two arguments:
    • [data1, data2]
    • { sheets: ['Sheet1', 'Sheet2'], columns: [columns1, columns2], ... }
  • New — one argument:
    • [
      • { data: data1, sheet: 'Sheet1', columns: columns1, ... },
      • { data: data2, sheet: 'Sheet2', columns: columns2, ... }
    • ]

• Changed the result of writeExcelFile() function.

  • Instead of receiving options such as fileName or filePath or buffer: true, etc, and then adjusting the return type based on those options, it now returns an object with several async toXxx() methods.
    • Old: await writeExcelFile(data, { filePath: '/path/to/output-file.xlsx' })
    • New: await writeExcelFile(data).toFile('/path/to/output-file.xlsx')

• If you were using schema parameter:

  • Removed schema parameter from writeExcelFile() function.
    • Use the new exported function getSheetData() instead.
      • Old: await writeExcelFile(objects, { schema })
      • New: await writeExcelFile(getSheetData(objects, schema))
  • In a schema, column property was renamed to header.
    • Old: [{ column: 'First Name', value: (person) => person.firstName }]
    • New: [{ header: 'First Name', value: (person) => person.firstName }]
  • In a schema, header property now represents a column header cell, so it can be not just a string but also an object with a value property and any optional cell style properties.
    • This means that the header style for each different column can be specified directly in a schema entry for that column.
  • In a schema, any cell properties such as value, type, format, fontWeight, etc were moved to a nested object called cell. Specifically, this cell property is a function of two arguments — object and objectIndex — which returns an object with the aforementioned cell properties. And the value property is no longer a "getter" function, it's a regular value.
  • Previously, it used to apply the default width: 14 to type: Date columns. It no longer does that.
    • Specify the width of such columns manually in a schema.
  • Removed getHeaderStyle parameter from writeExcelFile() function.
    • Use the new header property on each column in a schema to set the style for that column's header cell.
  • Previously, it used to apply bold font to the header row by default. It no longer does that.
    • Use the new header property on each column in a schema to set the style for that column's header cell.
  • If you were using getCellStyle() option:
    • Removed getCellStyle() option. It was replaced by the new cell() property in a column definition in a schema.

• If you were using features parameter:

  • The features parameter was moved from the second argument to the third argument (in case of a file with a single sheet).
  • If you implemented file.transform property of a feature:
    • Changed the first argument of files.transform.insert() / files.transform.transform() — it's now an array with each separate sheet's options.
    • Changed the second argument of files.transform.insert() / files.transform.transform():
      • Removed multipleSheetsParameters property because now all sheets' options are separate.
      • Removed attributeValue() and textContent() properties because they can be imported directly from write-excel-file/utility subpackage.
    • Removed files.transform.parameters() function. Any sheet options are now available to any feature.
  • If you implemented files.write property of a feature:

... (truncated)

Commits

• abd3222 4.0.2
• 88deff4 Fixed TypeScript
• 863acba 4.0.1
• 92517e7 Update README.md
• 76e6426 4.0.0
• b692752 Rewrote multi-sheet arguments
• See full diff 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.