yini-parser 1.0.1-beta → 1.1.0-beta

package/CHANGELOG.md

@@ -1,5 +1,38 @@
 # CHANGELOG
 
+## --dev/uppcoming--
+
+## 1.1.0-beta - 2025 Sep
+### Parser
+- **Reimplemented parser from scratch** (`core/ASTBuilder.ts`) using the refactored grammar for a much cleaner and more maintainable design.  
+- **Build logic reimplemented** (`core/objectBuilder.ts`) for improved reliability and consistency.  
+- **Error reporting enhanced** to be more user-friendly and informative.  
+- **Fixed bug sometimes wrong line** Sometimes incorrect line number in error messages are now reported accurately.
+- Renamed option `bailSensitivity` to a more shorter and user-friendly name `failLevel`.
+- **Extended `parse` and `parseFile` methods** to support an options-object form.  
+  Example:
+  ```ts
+  const config= YINI.parse(yini, {
+            strictMode: false,
+            failLevel: 'auto',
+            includeMetaData: false,
+            requireDocTerminator: false,
+        })  
+  ```  
+### Specification Alignment
+- Updated to follow the **latest YINI specification (v1.0.0-rc.3)**.  
+  - Document terminator `/END` is now optional in both lenient and strict mode.
+### Meta Data
+- The optional returned **meta data structure** has been redesigned.  
+  - Now includes improved organization.  
+  - **Timing support** added for detailed performance insight.
+  - Grouping with **source**, **structure**, **diagnostics**, etc.
+
+## 1.0.2-beta - 2025 Aug
+- Fixed issues with floats, including negative and exponential numbers with new test files here: `tests/fixed-issues/issue-32/*`
+- Fixed an issue where parseFile(..) did not output a warning when parsing a file missing a newline at EOF. Plus added test cases to check that it is fixed (in `tests/fixed-issues/issue-30`).
+- Fixed and improved number parsing to fully support negative values and edge cases for integers, floats, hex, bin, octal, duodecimal, and exponential numbers. Based on updated lexer and parser grammar files, and added extensive tests to ensure correct and robust handling. Here: `tests/integration/6-number-literals/*`
+
 ## 1.0.1-beta - 2025 Aug
 - Fixed catching lexer related errors correctly.
 - Improves error and test handling for invalid YINI syntax.

package/README.md

@@ -1,6 +1,6 @@
 # YINI Parser for Node.js
 
-YINI is a clean, minimal, and human-readable config format for structured configuration. This parser implements the YINI spec in TypeScript for Node.js, with support for nested sections, strict/lenient modes, and typed values.
+A TypeScript/Node.js parser for YINI — A type-safe, structured, and human-readable config format with nested sections, types, comments, and support for strict validation.
 
 [![npm version](https://img.shields.io/npm/v/yini-parser.svg)](https://www.npmjs.com/package/yini-parser) [![All Tests](https://github.com/YINI-lang/yini-parser-typescript/actions/workflows/run-all-tests.yml/badge.svg)](https://github.com/YINI-lang/yini-parser-typescript/actions/workflows/run-all-tests.yml)
 
@@ -13,7 +13,7 @@ import YINI from 'yini-parser'
 const config = YINI.parseFile('./config.yini')
 ```
 
-A clean, minimal, human-readable config format—designed as an alternative to INI, YAML, and JSON.
+YINI (Yet another INI): YINI is a configuration format designed for readability and structure, inspired by INI and YAML.
 
 ➡️ See full [documentation or YINI format specification](https://github.com/YINI-lang/YINI-spec)
 
@@ -21,7 +21,7 @@ A clean, minimal, human-readable config format—designed as an alternative to I
 
 ---
 
-## YINI Parser – TypeScript
+## YINI Parser – (source code in TypeScript)
 
 > 🚧 This package is in **beta**. The core API is stabilizing, some more advanced features may still change. Feedback and bug reports are welcome!
 
@@ -34,22 +34,49 @@ YINI is a simple, human-friendly configuration format inspired by INI and JSON.
 
 ---
 
+## 🙋‍♀️ Why YINI?
+- **YINI is an alternative** to other great config formats like INI, JSON, YAML, XML, and TOML — Supports section nesting and explicit syntax for configuration files.
+- **Started as a personal project and a research challenge:** Provides structure similar to INI, with features inspired by JSON and YAML.
+- **Built for clarity:**
+    * Uses a concise syntax to minimize unnecessary characters.
+    * Supports commonly used configuration structures.
+- *Developed to meet practical needs, driven by curiosity and a desire **for configuration clarity, simplicity, minimalism, and flexibility**.
+
+---
+
+## 💡 What is YINI?
+- **Simple like INI** — but with strong typing, comments, and nested sections.
+- **Provides concise, structured syntax** for configuration.
+- Supports section nesting **without requiring indentation or dot-delimited keys**.
+- This repo/parser is built for both **JavaScript and TypeScript**.
+- **Supports strict and lenient modes**, and all major data types.
+- Can be **edited manually** or **processed programmatically**.
+- 👉 See [how YINI compares with JSON, YAML, INI, and TOML](https://github.com/YINI-lang/yini-parser-typescript/tree/main/examples/compare-formats.md).
+- Want the full syntax reference? See the [YINI Specification](https://github.com/YINI-lang/YINI-spec).
+  
+---
+
 ## Quick Start
 
-A minimal example using YINI in TypeScript:
+A small example using YINI in TypeScript/JavaScript:
 ```ts
 import YINI from 'yini-parser'
 
 const config = YINI.parse(`
-^ App
-name     = 'My Title'    // App display name.
-items    = 25
-darkMode = true
-
-    // Sub-section of App.
-    ^^ Special
-    primaryColor = #336699
-    isCaching = false
+    // YINI is a simple, human-readable configuration file format.
+
+    // Note: In YINI, spaces and tabs don't change meaning - 
+    // indentation is just for readability.
+
+    ^ App                      // Definition of section (group) "App" 
+      name     = 'My Title'    // Keys and values are written as key = value
+      items    = 25
+      darkMode = true          // "ON" and "YES" works too
+
+        // Sub-section of the "App" section
+        ^^ Special
+           primaryColor = #336699   // Hex number format
+           isCaching    = false     // "OFF" and "NO" works too
 `)
 
 // To parse from a file instead:
@@ -67,246 +94,29 @@ My Title
 false
 
 {
-  App: {
-    name: 'My Title',
-    items: 25,
-    darkMode: true,
-    Special: { 
-      primaryColor: 3368601,
-      isCaching: false
+    App: {
+        name: 'My Title',
+        items: 25,
+        darkMode: true,
+        Special: { 
+            primaryColor: 3368601,
+            isCaching: false
+        }
     }
-  }
 }
 ```
 
 That's it!
 
-▶️ Link to [examples/](https://github.com/YINI-lang/yini-parser-typescript/tree/main/examples) files.
+- ▶️ Link to [examples/](https://github.com/YINI-lang/yini-parser-typescript/tree/main/examples) files.
+- ▶️ Link to [Demo Apps](https://github.com/YINI-lang/yini-demo-apps/tree/main) with complete basic usage.
 
-## 💡 Why YINI?
-- **Easy to read and write**, minimal syntax noise, maximum clarity.
-- **Clear and minimal section nesting** without painful indentation rules or long dot nested strings, etc.
-- A perfect alternative to messy JSON, legacy INI, or complex YAML.
-- Built for both **JavaScript and TypeScript**.
-- **Supports strict/lenient modes**, and all major data types.
-- Both **human-friendly**, and **machine-friendly**.
-- 👉 See [how YINI compares to JSON, YAML, INI, and TOML](https://github.com/YINI-lang/yini-parser-typescript/tree/main/examples/compare-formats.md).
-- Want the full syntax reference? See the [YINI Specification](https://github.com/YINI-lang/YINI-spec).
-  
 ---
 
 ## Intro to YINI Config Format
+**YINI** is a simple and readable configuration format. Sections are defined with `^ SectionName`, and values are assigned using `key = value`. The format supports common data types (same as those found in JSON), including strings, numbers, booleans, nulls, and lists. 
 
-### 1. Sections
-Group settings under a named header. A section header name starts with `^`.
-
-Start a section with `^`, e.g.:
-```yini
-^ App
-title = "AppName"
-```
-
-> Alternative section markers to `^` are also supported: `<`, `§`, `€` (e.g. `< Section`).
-
-> See section 9 for more advanced marker and naming options.
-
-### 2. Key = Value
-Each line inside a section is a **key** (name) and **value**, separated by `=`.
-
-Write settings as `key = value`:
-```yini
-maxConnections = 100
-enableLogging  = true
-```
-
-> See section 9 for more advanced marker and naming options.
-
-#### 💡Tip
-Use backticks (\`) to quote section or key names that contain spaces or special characters.
-
-Key names with spaces/special characters can be backticked:
-
-```yini
- user id  = 1            # Invalid ❌
-`user id` = 1            # Valid ✅
-```
-
-### 3. Values
-Values can be:
-- **Strings** (always quoted): `'hello'` or `"world"` (either single or double quoted)
-- **Numbers:** `42`, `3.14` or `-10`
-- **Booleans:** `true`, `false`, `on`, `off`, `yes`, `no` (all case-insensitive)
-- **Nulls:** Use `null` or leave the value blank after `=` (in lenient mode)
-- **Lists:**
-  * JSON‑style: `["red", "green", "blue"]`
-  * Colon‑style: *(Planned – not yet implemented in parser)* 
-
-### 4. Comments
-Various commenting styles are supported:
-```yini
-// This is a line comment
-timeout = 30  // inline comment
-# This is also a line comment (must have a space after #)
-interval = 30  # inline comment (must have a space after #)
-/* Block comment spanning
-   multiple lines */
-; Full line comment (must be whole line).
-```
-
-> **Tip:** You can add comments anywhere—above, beside, or below any setting or section.
-> 
-👆 **Caveat 1:** If you use `#` for comments, always put a space after the `#`.
-(Otherwise, the parser might misinterpret it as part of a value.)
-
-👆 **Caveat 2:** `;` is used only for full-line comments. The `;` must be the first non-whitespace character on a line (only spaces or tabs are allowed before it).
-(If `;` appears later in the line, the parser may treat it as part of a value or as a line delimiter, not as a comment.)
-
-💡**Tip:** You can use any comment style in your file.
-For best readability, try to stick to one style per file.
-
-### 5. Nested Sections
-Use extra carets `^` for sub‑sections:
-```yini
-^ Parent
-^^ Child
-
-// Add another caret `^` and you get a sub-section
-// of the previous section, and so...
-^^^ SubChild
-```
-
-If you prefer, you can indent the nested section for visibility:
-```yini
-^ Main
-    ^^ Sub
-    host = "db.example.com"
-```
-
-One can nest multiple sections:
-```yini
-^ Root
-^^ Sub
-^^^ SubSub
-^ BackToRoot
-```
-
-Example with indented sections:
-```yini
-^ Root
-value = 'At level 1'
-    ^^ Sub
-    value = 'At level 2'
-        ^^^ SubSub
-        value = 'At level 3'
-        
-^ BackToRoot
-value = 'Back at level 1'
-```
-
-The above Yini code will produce the following JavaScript object:
-```js
-// JS object
-{
-  Root: {
-    value: 'At level 1',
-    Sub: { value: 'At level 2', SubSub: { value: 'At level 3' } }
-  },
-  BackToRoot: { value: 'Back at level 1' }
-}
-```
-
-> See section 9 for more advanced marker and naming options.
-
-### 6. Lists
-```yini
-// JSON‑style lists
-colors = ["red", "green", "blue"]
-
-numberList = [
-    10,
-    20,
-    30
-]
-
-
-// Colon‑style list
-// 👆 Colon‑style list support is planned for an upcoming release.
-fruits:
-  "Pear",
-  "Cherry",
-  "Banana"
-```
-
-> You can use either single or double quotes for string values in YINI.
-
-### 7. Document Terminator (strict mode)
-The `/END` marker is required only in strict mode, and optional in lenient (default) mode.
-
-End a file explicitly with:
-```yini
-^ App
-title = "MyTitle"
-
-/END    // Must be included in strict mode.
-```
-
-### 8. Disabled Lines
-Prefix any valid line with `--` to skip it entirely:
-```yini
---maxRetries = 5
-```
-
-### 9. Advanced: Alternative Section Markers & Naming
-In addition to the standard syntax, YINI supports several advanced options:
-
-- (a.) **Alternative section markers:**  
-  Besides `^`, you can use `<`, `§`, or `€` as section header markers.  
-  
-  ```yini
-  < MySection
-  § Settings
-  € MyApp
-  ```
-
-- (b.) **Backticked section names and key names:**  
-  Use backticks (`) to allow spaces or special characters in section or key names:
-
-  ```yini
-    ^ `Section name with spaces`
-    `user id` = 42
-  ```
-
-- (c.) **Numeric shorthand section markers:**  
-  To create deeply nested sections (beyond 6 levels), use numeric shorthand:
-
-  ```yini
-  ^7 DeepSection    # Equivalent to 7 carets: ^^^^^^^ DeepSection
-  <10 VeryDeep      # Equivalent to <<<<<<<<<<< VeryDeep
-  ```
-
-  👆 Though, can not mix standard/classic and numeric shorthand markers in the same section header.
-
-- (d.) **More features:**  
-  The YINI format supports even more features than listed here, such as additional number notations, string types, and advanced escaping. For full details, see the [latest release of the YINI specification](https://github.com/YINI-lang/YINI-spec/blob/release/YINI-Specification.md).
-
-### 10. Complete Example
-
-```yini
-@yini       # Optional marker to identify YINI format.
-
-^ App
-name    = "MyApp"
-version = "1.0.0"
-debug   = off  // Turn on for debugging.
-
-^^ Database
-host     = "db.local"
-port     = 5432
---user   = "secret"  # This line is disabled due to --.
-userList = ["alice", "bob", "carol"]
-
-/END
-```
+To learn more, see the [Getting Started: Intro to YINI Config Format](https://github.com/YINI-lang/YINI-spec/blob/develop/Docs/Intro-to-YINI-Config-Format.md) tutorial.
 
 ---
 
@@ -424,45 +234,44 @@ These examples are also included in the npm package.
 
 ---
 
-## Advanced Example
+## Bigger Example
 
 ```js
 const YINI = require('yini-parser').default; // Or: import YINI from 'yini-parser';
 
 const config = YINI.parse(`
-    /*
-        This is a multi-line block comment.
+    // This is a comment in YINI
+    // YINI is a simple, human-readable configuration file format.
+
+    // Note: In YINI, spaces and tabs don't change meaning - indentation is just
+    // for readability.
+
+    /*  This is a block comment
+
+        In YINI, section headers use repeated characters "^" at the start to
+        show their level: (Section header names are case-sensitive.)
+
+        ^ SectionLevel1
+        ^^ SectionLevel2
+        ^^^ SectionLevel3
     */
 
-    @yini
+    ^ App                           // Definition of section (group) "App" 
+      title = 'My App'
+      items = 25
+      debug = ON                    // "true" and "YES" works too
 
-    ^ App
-    name = "Nested Example"
-    version = "1.0.0"
-    debug = OFF  // This is a comment.
-
-        # Database settings.
-        ^^ Database
-        host = "db.example.com"
-        port = 3306
-        user = "appuser"
-        --password = "dbpassword"  # Disabled line due to --.
-        //password = "dbpassword"  # Not sure yet about this pw.
-        password = "dbpassword"  # Keep this secret.
-
-            // Commenting with slashes works too.
-            ^^^ Pool
-            min = 2
-            max = 10
-            idleTimeout = 300
-
-        /* Block comment on a single line. */
-        ^^ Logging
-        level = "info"
-        logToFile = ON # This is a comment.
-        filePath = "./logs/app.log"
+    ^ Server                        // Definition of section (group) "Server"
+      host = 'localhost'
+      port = 8080
+      useTLS = OFF                  // "false" and "NO" works too
+
+        // Sub-section of "Server"
+        ^^ Login
+          username = 'user_name'
+          password = 'your_password_here'
     
-    /END
+    /END // (only optional)
 `);
 
 console.log(config);
@@ -473,60 +282,41 @@ console.log(config);
 // JS object
 {
     App: {
-        name: "Nested Example",
-        version: "1.0.0",
-        debug: false,
-        Database: {
-            host: "db.example.com",
-            port: 3306,
-            user: "appuser",
-            password: "dbpassword",
-            Pool: {
-                min: 2,
-                max: 10,
-                idleTimeout: 300
-            }
-        },
-        Logging: {
-            level: "info",
-            logToFile: true,
-            filePath: "./logs/app.log"
+        title: 'My App', 
+        items: 25, 
+        debug: true
+    },
+    Server: {
+        host: 'localhost',
+        port: 8080,
+        useTLS: false,
+        Login: { 
+            username: 'user_name', 
+            password: 'your_password_here'
         }
     }
 }
 ```
 
----
-
-## API
-
-Only the `YINI` class is exposed in the public API, with two static methods: `parse` and `parseFile`.
-
-### `YINI.parse(yiniContent: string, strictMode?: boolean, bailSensitivity: 'auto' | 0 | 1 | 2 = "auto", includeMetaData = false): object`
-
-Parses YINI code from a string.  
-
-**Params:**
-- `yiniContent`: The YINI configuration as a string.
-- `strictMode`: (optional, default `false`) Parse in strict mode.
-- `bailSensitivity`: (optional, default `"auto"`) Error tolerance level.
-  * If `bailSensitivity` is `"auto"` then bail sensitivity level will be set to 0 if in non-strict mode, if in strict mode then level 1 will be used automatically.
-- `includeMetaData`: If true then additional meta data will be returned along the object.
-
-**Bail sensitivity levels:**
-- 0 = 'Ignore-Errors' // Don't bail on errors, persist and try to recover.
-- 1 = 'Abort-on-Errors'
-- 2 = 'Abort-Even-on-Warnings'
-
-Returns a JavaScript object representing the parsed configuration (YINI content).
-
-### `YINI.parseFile(filePath: string, strictMode?: boolean, bailSensitivity: 'auto' | 0 | 1 | 2 = "auto", includeMetaData = false): object`
-
-Parses YINI code from a file.
-- `filePath`: Path to the `.yini` file.
-- Other parameters are the same as `parse(..)`.
-
-Returns a JavaScript object representing the parsed YINI configuration file.
+### Output in JSON:
+```json
+{
+    "App": {
+        "title": "My App",
+        "items": 25,
+        "debug": true
+    },
+    "Server": {
+        "host": "localhost",
+        "port": 8080,
+        "useTLS": false,
+        "Login": {
+            "username": "user_name",
+            "password": "your_password_here"
+        }
+    }
+}
+```
 
 ---
 
@@ -544,13 +334,26 @@ We welcome feedback, bug reports, feature requests, and code contributions!
 ---
 
 ## Links
-- ➡️ [Why YINI? Why another format!?](./RATIONALE.md) (rationale)
-- ➡️ [Intro to YINI Config Format](https://github.com/YINI-lang/yini-parser-typescript?tab=readme-ov-file#intro-to-yini-config-format) (learn YINI)
-- ➡️ [Read the YINI Specification](./YINI-Specification.md#table-of-contents) (spec)
-- ➡️ [Official YINI Parser on npm](https://www.npmjs.com/package/yini-parser) (npm)
-- ➡️ [YINI Parser GitHub Repo](https://github.com/YINI-lang/yini-parser-typescript) (GitHub)
-- ➡️ [YINI vs Other Formats](https://github.com/YINI-lang/YINI-spec/blob/develop/Docs/Examples%20of%20YINI%20vs%20Other%20Formats.md)
-- ➡️ [YINI Project](https://github.com/YINI-lang) (home)
+- ➡️ [Getting Started: Intro to YINI Config Format](https://github.com/YINI-lang/YINI-spec/blob/develop/Docs/Intro-to-YINI-Config-Format.md)  
+  *Beginner-friendly walkthrough and basic usage examples.*
+
+- ➡️ [YINI Parser on npm](https://www.npmjs.com/package/yini-parser)  
+  *Install and view package details.*
+
+- ➡️ [Read the YINI Specification](https://github.com/YINI-lang/YINI-spec/blob/release/YINI-Specification.md#table-of-contents)  
+  *Full formal spec for the YINI format, including syntax and features.*
+
+- ➡️ [YINI CLI on GitHub](https://github.com/YINI-lang/yini-cli)  
+  *TypeScript source code, issue tracker, and contributing guide.*
+
+- ➡️ [YINI vs Other Formats](https://github.com/YINI-lang/YINI-spec/tree/release#-summary-difference-with-other-formats)  
+  *How does YINI differ: comparison with INI, YAML, and JSON.*
+  
+- ➡️ [Why YINI? (Project Rationale)](https://github.com/YINI-lang/YINI-spec/blob/release/RATIONALE.md)  
+  *Learn about the motivations and design decisions behind YINI.*
+
+- ➡️ [YINI Project](https://github.com/YINI-lang)  
+  *YINI home.*
 
 ---
 

package/dist/YINI.d.ts

@@ -1,43 +1,66 @@
-import { TJSObject } from './core/types';
+import { IAllUserOptions, TJSObject, TPreferredFailLevel } from './core/types';
 /**
  * This class is the public API, which exposes only parse(..) and
  * parseFile(..), rest of the implementation details are hidden.
  * @note Only parse and parseFile are public.
  */
 export default class YINI {
-    static filePath: string;
+    private static g_tabSize;
     /**
-     * Parse YINI content into a JavaScript object.
+     * @returns The number of spaces per tab character used in error messages.
+     */
+    static getTabSize(): number;
+    /**
+     * Overrides the number of spaces per tab character used in error messages.
+     * Allowed range: 1-32.
+     */
+    static setTabSize(spaces: number): void;
+    /**
+     * Parse inline YINI content into a JavaScript object.
      *
      * @param yiniContent      YINI code as a string (multi‑line content supported).
      * @param strictMode       If `true`, enforce strict parsing rules (e.g. require `/END`, disallow trailing commas).
-     * @param bailSensitivity  Controls how errors and warnings are handled:
-     *   - `'auto'`               : Auto‑select level (strict→1, lenient→0)
+     * @param failLevel        Preferred bail sensitivity level, controls how errors and warnings are handled:
+     *   - `'auto'` (default)       : Auto‑select level (strict→1, lenient→0)
      *   - `0` / `'Ignore-Errors'`    : Continue parsing despite errors; log them and attempt recovery.
      *   - `1` / `'Abort-on-Errors'`  : Stop parsing on the first error.
      *   - `2` / `'Abort-Even-on-Warnings'`: Stop parsing on the first warning **or** error.
      * @param includeMetaData  If `true`, return additional metadata (e.g. warnings, statistics) alongside the parsed object.
      *
-     * @note The order of properties in each output object may differ from their order in the YINI source.
+     * @returns A JavaScript object representing the parsed YINI content.
+     */
+    static parse(yiniContent: string, strictMode?: boolean, failLevel?: TPreferredFailLevel, includeMetaData?: boolean): TJSObject;
+    /**
+     * Parse inline YINI content into a JavaScript object, using an options object for configuration.
+     *
+     * @param yiniContent      YINI code as a string (multi‑line content supported).
+     * @param options Optional settings to customize parsing and/or results, useful if you need more control.
      *
      * @returns A JavaScript object representing the parsed YINI content.
      */
-    static parse: (yiniContent: string, strictMode?: boolean, bailSensitivity?: "auto" | 0 | 1 | 2, includeMetaData?: boolean) => TJSObject;
+    static parse(yiniContent: string, options?: IAllUserOptions): TJSObject;
     /**
      * Parse a YINI file into a JavaScript object.
      *
      * @param yiniFile Path to the YINI file.
      * @param strictMode       If `true`, enforce strict parsing rules (e.g. require `/END`, disallow trailing commas).
-     * @param bailSensitivity  Controls how errors and warnings are handled:
-     *   - `'auto'`               : Auto‑select level (strict→1, lenient→0)
+     * @param failLevel        Preferred bail sensitivity level, controls how errors and warnings are handled:
+     *   - `'auto'` (default)       : Auto‑select level (strict→1, lenient→0)
      *   - `0` / `'Ignore-Errors'`    : Continue parsing despite errors; log them and attempt recovery.
      *   - `1` / `'Abort-on-Errors'`  : Stop parsing on the first error.
      *   - `2` / `'Abort-Even-on-Warnings'`: Stop parsing on the first warning **or** error.
      * @param includeMetaData  If `true`, return additional metadata (e.g. warnings, statistics) alongside the parsed object.
      *
-     * @note The order of properties in each output object may differ from their order in the YINI source.
+     * @returns A JavaScript object representing the parsed YINI content.
+     */
+    static parseFile(filePath: string, strictMode?: boolean, failLevel?: TPreferredFailLevel, includeMetaData?: boolean): TJSObject;
+    /**
+     * Parse a YINI file into a JavaScript object, using an options object for configuration.
+     *
+     * @param yiniFile Path to the YINI file.
+     * @param options Optional settings to customize parsing and/or results, useful if you need more control.
      *
      * @returns A JavaScript object representing the parsed YINI content.
      */
-    static parseFile: (filePath: string, strictMode?: boolean, bailSensitivity?: "auto" | 0 | 1 | 2, includeMetaData?: boolean) => TJSObject;
+    static parseFile(filePath: string, options?: IAllUserOptions): TJSObject;
 }