Releases: harshankur/officeParser
Releases · harshankur/officeParser
Release list
v5.2.2
v5.2.2 - 12.11.2025
Changes: v5.2.1..v5.2.2
-
Fixed #69 where Excel numbers were parsed as Int even when they didn't represent index in sharedStrings array. Further, the extracted float numbers from openOffice files were not precise enough. Fixed that too.
-
Fixed #66 where order of text would get messed up when part of a text in a cell differs in formatting.
v5.2.1
v5.2.1 - 29.09.2025
Changes: v5.2.0..v5.2.1
v5.2.0
v5.2.0 - 05.07.2025
Changes: v5.1.1..v5.2.0
- Fixed #36 by upgrading pdfjs-dist version to the latest v5.3.31.
- Added pdfjs-dist as an npm dependency instead of using an older local library which unnecessarily increases this library's size.
Breaking Changes:
- The new version of pdfjs-dist requires node >= v18. Please ensure you upgrade node before using this version.
- Browser bundle of officeParser does not work for pdf files with this release. Please use the artifacts from the previous release v5.1.0 including the worker file. Text extraction for all other supported files work fine in browsers with the bundle artifact of this release as well.
v5.1.0
v5.1.0 - 12.11.2024
Changes: v5.0.0..v5.1.0
What's Changed
- Added support for ArrayBuffer as file input.
- Fixed #35 which was a request to create browser version by creating bundle.js files available as part of release asset which exposes officeParser as a namespace.
- To use the bundle in a browser, add both files on the same directory as your html file which sources this bundle. For pdf files, the bundle uses the worker automatically. It is not needed for parsing office files.
- In the script part of your code, you can use officeParser by using
officeParser.parseOfficeAsync.
v5.0.0
Version 5.0.0 🎉
What's Changed
- Replaced using decompress with yauzl. Extracting zip files in memory now instead of storage. Therefore, the requirement for a temp directory to unload the internal xml files of the office files is now eliminated. This fixes #16, #34, #45.
- Improved CLI executions with better checks and support for supplying config flags as arguments
Breaking Changes?
All the changes are backward compatible for vanilla javascript users.
But typescript and jsdoc users may look into the OfficeParserConfig that you supply to parseOffice and parseOfficeAsync as they have the following two keys removed from the object which may break your code in compile time.
- tempFilesLocation
- preserveTempFiles