officeparser 4.2.0 → 5.1.1

package/README.md

@@ -13,6 +13,8 @@ A Node.js library to parse text out of any office file.
 
 
 #### Update
+* 2024/11/12 - Added ArrayBuffer as a type of file input. Generating bundle files now which exposes namespace officeParser to be able to access parseOffice and parseOfficeAsync directly on the browser. Extracting text out of pdf files does not work currently in browser bundles.
+* 2024/10/21 - Replaced extracting zip files from decompress to yauzl. This means that we now extract files in memory and we no longer need to write them to disk. Removed config flags related to extracted files. Added flags for CLI execution.
 * 2024/10/15 - Fixed erroring out while deleting temp files when multiple worker threads make parallel executions resulting in same file name for multiple files. Fixed erroring out when multiple executions are made without waiting for the previous execution to finish which resulted in deleting the file from other execution. Upgraded dependencies.
 * 2024/10/13 - Fixed parsing text from xlsx files which contain no shared strings file and files which have inlineStr based strings.
 * 2024/05/06 - Replaced pdf parsing support from pdf-parse library to natively building it using pdf.js library from Mozilla by analyzing its output. Added pdfjs-dist build as a local library.
@@ -37,7 +39,6 @@ A Node.js library to parse text out of any office file.
 
 ## Install via npm
 
-
 ```
 npm i officeparser
 ```
@@ -45,14 +46,20 @@ npm i officeparser
 ## Command Line usage
 If you want to call the installed officeParser.js file, use below command
 ```
-node </path/to/officeParser.js> <fileName>
+node <path/to/officeParser.js> [--configOption=value] [FILE_PATH]
+node officeparser [--configOption=value] [FILE_PATH]
 ```
 
-Otherwise, you can simply use npx to instantly extract parsed data.
+Otherwise, you can simply use npx without installing the node module to instantly extract parsed data.
 ```
-npx officeparser <fileName>
+npx officeparser [--configOption=value] [FILE_PATH]
 ```
 
+### Config Options:
+- `--ignoreNotes=[true|false]`          Flag to ignore notes from files like PowerPoint. Default is false.
+- `--newlineDelimiter=[delimiter]`      The delimiter to use for new lines. Default is `\n`.
+- `--putNotesAtLast=[true|false]`       Flag to collect notes at the end of files like PowerPoint. Default is false.
+- `--outputErrorToConsole=[true|false]` Flag to output errors to the console. Default is false.
 
 ## Library Usage
 ```js
@@ -101,8 +108,6 @@ officeParser.parseOfficeAsync(fileBuffers);
 *Optionally add a config object as 3rd variable to parseOffice for the following configurations*
 | Flag                 | DataType | Default          | Explanation                                                                                                                                                                                                                                     |
 |----------------------|----------|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| tempFilesLocation    | string   | officeParserTemp | The directory where officeparser stores the temp files . The final decompressed data will be put inside officeParserTemp folder within your directory. **Please ensure that this directory actually exists.** Default is officeParserTemp.      |
-| preserveTempFiles    | boolean  | false            | Flag to not delete the internal content files and the possible duplicate temp files that it uses after unzipping office files. Default is false. It always deletes all of those files.                                                          |
 | outputErrorToConsole | boolean  | false            | Flag to show all the logs to console in case of an error. Default is false.                                                                                                                                                                     |
 | newlineDelimiter     | string   | \n               | The delimiter used for every new line in places that allow multiline text like word. Default is \n.                                                                                                                                             |
 | ignoreNotes          | boolean  | false            | Flag to ignore notes from parsing in files like powerpoint. Default is false. It includes notes in the parsed text by default.                                                                                                                  |
@@ -157,7 +162,7 @@ function searchForTermInOfficeFile(searchterm, filepath) {
 
 **Example - TypeScript**
 ```ts
-const officeParser = require('officeparser');
+import { OfficeParserConfig, parseOfficeAsync } from 'officeparser';
 
 const config: OfficeParserConfig = {
     newlineDelimiter: " ",  // Separate new lines with a space instead of the default \n.
@@ -165,7 +170,7 @@ const config: OfficeParserConfig = {
 }
 
 // relative path is also fine => eg: files/myWorkSheet.ods
-officeParser.parseOfficeAsync("/Users/harsh/Desktop/files/mySlides.pptx", config);
+parseOfficeAsync("/Users/harsh/Desktop/files/mySlides.pptx", config);
     .then(data => {
         const newText = data + " look, I can parse a powerpoint file";
         callSomeOtherFunction(newText);
@@ -174,17 +179,58 @@ officeParser.parseOfficeAsync("/Users/harsh/Desktop/files/mySlides.pptx", config
 
 // Search for a term in the parsed text.
 function searchForTermInOfficeFile(searchterm: string, filepath: string): Promise<boolean> {
-    return officeParser.parseOfficeAsync(filepath)
+    return parseOfficeAsync(filepath)
         .then(data => data.indexOf(searchterm) != -1)
 }
 ```
 \
 **Please take note: I have breached convention in placing err as second argument in my callback but please understand that I had to do it to not break other people's existing modules.**
 
+## Browser Usage
+Download the bundle file available as part of the release asset.
+Include this bundle file in your browser html file and access `parseOffice` and `parseOfficeAsync` under the **`officeParser`** namespace.
+
+**Example**
+```html
+<head>
+    ...
+    <!-- Include bundle file in the script tag. -->
+    <script src="officeParserBundle@5.1.0.js"></script>
+</head>
+<body>
+    ...
+    <input type="file" id="fileInput" />
+    ...
+    <script>
+        document.getElementById('fileInput').addEventListener('change', async function(event) {
+            const outputDiv = document.getElementById('output');
+            const file = event.target.files[0];
+            try {
+                // Your configuration options for officeParser
+                const config = {
+                    outputErrorToConsole: false,
+                    newlineDelimiter: '\n',
+                    ignoreNotes: false,
+                    putNotesAtLast: false
+                };
+
+                const arrayBuffer = await file.arrayBuffer();
+                const result = await officeParser.parseOfficeAsync(arrayBuffer, config);
+                // result contains the extracted text.
+            }
+            catch (error) {
+                // Handle error
+            }
+        });
+    </script>
+</body>
+```
+
 
 ## Known Bugs
 1. Inconsistency and incorrectness in the positioning of footnotes and endnotes in .docx files where the footnotes and endnotes would end up at the end of the parsed text whereas it would be positioned exactly after the referenced word in .odt files.
 2. The charts and objects information of .odt files are not accurate and may end up showing a few NaN in some cases.
+3. Extracting texts in browser bundles does not work for pdf files.
 ----------
 
 **npm**