sf-decomposer 5.4.0 → 5.4.2

package/CHANGELOG.md

@@ -5,6 +5,21 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+## [5.4.2](https://github.com/mcarvin8/sf-decomposer/compare/v5.4.1...v5.4.2) (2025-03-21)
+
+
+### Bug Fixes
+
+* **deps:** bump @salesforce/source-deploy-retrieve ([f074b4f](https://github.com/mcarvin8/sf-decomposer/commit/f074b4f90ab149e064eb88892e0846e90a501984))
+* **deps:** bump the xml-disassemblers group with 4 updates ([abe8ec7](https://github.com/mcarvin8/sf-decomposer/commit/abe8ec7d53b88ecdd8131eb32c80fadfe51c73f4))
+
+## [5.4.1](https://github.com/mcarvin8/sf-decomposer/compare/v5.4.0...v5.4.1) (2025-03-14)
+
+
+### Bug Fixes
+
+* **deps:** bump @salesforce/source-deploy-retrieve ([e636bb9](https://github.com/mcarvin8/sf-decomposer/commit/e636bb975a661e7018c99bbf17f359ac7c86747b))
+
 ## [5.4.0](https://github.com/mcarvin8/sf-decomposer/compare/v5.3.13...v5.4.0) (2025-03-07)
 
 

package/README.md

@@ -1,4 +1,4 @@
-# sf-decomposer
+# `sf-decomposer`
 
 [![NPM](https://img.shields.io/npm/v/sf-decomposer.svg?label=sf-decomposer)](https://www.npmjs.com/package/sf-decomposer) [![Downloads/week](https://img.shields.io/npm/dw/sf-decomposer.svg)](https://npmjs.org/package/sf-decomposer) [![License](https://img.shields.io/badge/License-MIT-yellow.svg)](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/LICENSE.md)
 
@@ -7,7 +7,7 @@
   <summary>Table of Contents</summary>
 
 - [Quick Start](#quick-start)
-- [Why SF Decomposer](#why-sf-decomposer)
+- [Why Choose `sf-decomposer`](#why-choose-sf-decomposer)
 - [Commands](#commands)
   - [`sf decomposer decompose`](#sf-decomposer-decompose)
   - [`sf decomposer recompose`](#sf-decomposer-recompose)
@@ -21,11 +21,12 @@
   - [`.sfdecomposerignore`](#.sfdecomposerignore)
   - [`.gitignore`](#.gitignore)
 - [Issues](#issues)
+- [Built With](#built-with)
 - [Contributing](#contributing)
 - [License](#license)
 </details>
 
-Break down large Salesforce metadata files into smaller, more manageable files for version control and then recreate deployment-compatible files.
+Break down large Salesforce metadata files (XML) into smaller, more manageable files (XML/JSON/YAML/JSON5) for version control and then recreate deployment-compatible files.
 
 ## Quick Start
 
@@ -41,13 +42,13 @@ sf plugins install sf-decomposer@x.y.z
 sf decomposer decompose -m "flow" -m "labels"
 ```
 
-3. Add decomposed files to `.forceignore`
+3. Add decomposed files to [`.forceignore`](#.forceignore)
 
-> This is **REQUIRED** to avoid errors when running `sf`commands. See [Ignore Files](#ignore-files) section.
+> This is **REQUIRED** to avoid errors when running `sf`commands
 
-4. Stage files in version control
+4. Stage decomposed files in version control
 
-5. [Recompose](#sf-decomposer-recompose) the metadata type(s)
+5. [Recompose](#sf-decomposer-recompose) the metadata type(s) before deployment
 
 ```bash
 sf decomposer recompose -m "flow" -m "labels"
@@ -55,21 +56,25 @@ sf decomposer recompose -m "flow" -m "labels"
 
 6. Deploy recomposed metadata
 
-## Why SF Decomposer
+## Why Choose `sf-decomposer`  
 
-Why should you consider using `sf-decomposer` over Salesforce's decomposition?
+Salesforce's built-in decomposition has limitations. `sf-decomposer` offers more control, flexibility, and versioning benefits for Admins and Developers.  
 
-- **Broad Metadata Support**: Unlike Salesforce's decomposition, `sf-decomposer` supports most metadata types available in the Metadata API.
-- **Selective Decomposition**: `sf-decomposer` allows you to decompose only the metadata you need instead of Salesforce's all-or-nothing approach.
-  - See [.sfdecomposerignore](#.sfdecomposerignore)
-- **Complete Decomposition**: Partially decomposed metadata types (e.g., Salesforce's `decomposePermissionSetBeta2`) can be fully decomposed by `sf-decomposer`.
-- **Consistent Sorting**: `sf-decomposer` recomposition ensures elements are always sorted consistently for better version control.
-- **Multiple Decompose Formats**: `sf-decomposer` allows you to decompose the original XML file into smaller XML, JSON, JSON5, or YAML files depending on your preference.
+### Key Advantages  
 
-In general, `sf-decomposer` helps Salesforce Admins do a few things with their source deployments:
+- **Supports More Metadata** – Works with most Metadata API types, unlike Salesforce’s limited decomposition.  
+- **Selective Decomposition** – Decompose only what you need, avoiding Salesforce’s all-or-nothing approach.  
+  - See [.sfdecomposerignore](#.sfdecomposerignore)  
+- **Fully Decomposes Metadata** – Ensures complete decomposition for types that Salesforce only partially decomposes (e.g., `decomposePermissionSetBeta2`).  
+- **Consistent Sorting** – Keeps elements in a predictable order to reduce unnecessary version control noise.  
+- **Multiple Output Formats** – Supports XML, JSON, JSON5, and YAML for greater flexibility.  
+- **CI/CD Integration** – Hooks enable seamless decomposition and recomposition in automated workflows.  
+- **Improved Version Control** – Smaller, structured files make pull requests easier to review and reduce merge conflicts.  
 
-- Enhance peer reviews of large metadata in CI/CD platforms like GitHub, i.e. easier-to-review diffs in pull requests
-- Make deployments safer by ensuring only the intended changes are deployed, improving the overall version control process
+### How It Helps Salesforce Teams  
+
+- **Better Peer Reviews** – More readable diffs for large metadata in GitHub and other CI/CD platforms.  
+- **Safer Deployments** – Ensures only intended changes are deployed, improving release quality.
 
 ## Commands
 
@@ -106,19 +111,14 @@ FLAGS
 GLOBAL FLAGS
   --json  Format output as json.
 
-DESCRIPTION
-  Decompose large metadata files into smaller files.
-
-  You should run this after you retrieve metadata from an org.
-
 EXAMPLES
-  Decompose all flows:
+  Decompose all flows in XML format:
 
     $ sf decomposer decompose -m "flow" -f "xml" --prepurge --postpurge --debug
 
-  Decompose all flows and custom labels:
+  Decompose all flows and custom labels in YAML format
 
-    $ sf decomposer decompose -m "flow" -m "labels" -f "xml" --prepurge --postpurge --debug
+    $ sf decomposer decompose -m "flow" -m "labels" -f "yaml" --prepurge --postpurge --debug
 
   Decompose flows except for those in the "force-app" package directory.
 
@@ -152,19 +152,14 @@ FLAGS
 GLOBAL FLAGS
   --json  Format output as json.
 
-DESCRIPTION
-  Recompose the decomposed files into deployment-compatible metadata files.
-
-  You should run this before you deploy decomposed metadata to an org.
-
 EXAMPLES
   Recompose all flows:
 
     $ sf decomposer recompose -m "flow" -f "xml" --postpurge --debug
 
-  Recompose all flows and custom labels:
+  Recompose all decomposed flows and custom labels YAMLs into XMLs
 
-    $ sf decomposer recompose -m "flow" -m "labels" -f "xml" --postpurge --debug
+    $ sf decomposer recompose -m "flow" -m "labels" -f "yaml" --postpurge --debug
 
   Recompose flows except for those in the "force-app" package directory.
 
@@ -199,7 +194,7 @@ When custom labels are decomposed, each custom label will have its own file in t
 
 All parent metadata types imported from this plugin's version of `@salesforce/source-deploy-retrieve` (SDR) toolkit are supported except for certain types.
 
-The `--metadata-type`/`-m` flag should be the metadata's `suffix` value as listed in the [metadataRegistry.json](https://github.com/forcedotcom/source-deploy-retrieve/blob/main/src/registry/metadataRegistry.json).
+The `--metadata-type`/`-m` flag should be the metadata's `suffix` value as listed in the [metadataRegistry.json](https://github.com/forcedotcom/source-deploy-retrieve/blob/main/src/registry/metadataRegistry.json). You can also infer the suffix by looking at the original XML file-name, i.e. `*.{suffix}-meta.xml`.
 
 Here are some examples:
 
@@ -210,7 +205,6 @@ Here are some examples:
 - AI Scoring Model Definition (`--metadata-type "aiScoringModelDefinition"`)
 - Decision Matrix Definition (`--metadata-type "decisionMatrixDefinition"`)
 - Bot (`--metadata-type "bot"`)
-  - **NOTE**: Running "bot" will also decompose and recompose Bot Version meta files. The `botVersion` meta suffix will be blocked from running directly.
 - Marketing App Extension (`--metadata-type "marketingappextension"`)
 
 ### Metadata Exceptions
@@ -240,36 +234,38 @@ Here are some examples:
 Error (1): sfdx-project.json not found in any parent directory.
 ```
 
-The `xml-disassembler` package will log errors, and optionally debugging statements, to a log file, `disassemble.log`. This log will be created in the working directory and will be created when running this plugin at all times. If there were no errors, this log will be empty. By default, the log will only contain errors. This plugin will print the errors as warnings in the command terminal to allow all other files to be processed. These warnings when decomposing or recomposing will look like:
+The `xml-disassembler` package will create a log file, `disassemble.log`, at all times. By default, the log will only contain XML decomposing/recomposing errors. XML decomposing/recomposing errors do not cause the Salesforce CLI to fail. The CLI will proceed to decompose/recompose all remaining metadata.
+
+The Salesforce CLI will print XML errors as warnings in the terminal:
 
 ```
 Warning: C:\Users\matth\Documents\sf-decomposer\test\baselines\flows\Get_Info\actionCalls\Get_Info.actionCalls-meta.xml was unabled to be parsed and will not be processed. Confirm formatting and try again.
 ```
 
-To add additional debugging statements to the log file, provide the `--debug` flag to the decompose or recompose command. Debugging statements will look like:
+To add debugging to the log, provide the `--debug` flag to the decompose or recompose command.
 
 ```
 [2024-03-30T14:28:37.959] [DEBUG] default - Created disassembled file: mock\no-nested-elements\HR_Admin\HR_Admin.permissionset-meta.xml
 ```
 
-Recommend adding the `disassemble.log` to your `.gitignore` file if you are using this in a git-based repo.
-
 ## Hooks
 
-> **NOTE:** In order to avoid errors when running `sf` commands, you must configure your `.forceignore` file to have the Salesforce CLI ignore the decomposed files. See [Ignore Files](#ignore-files) section.
+> **NOTE:** In order to avoid errors when running `sf` commands, you must configure your `.forceignore` file to have the Salesforce CLI ignore the decomposed files. See [Ignore Files](#ignore-files).
+
+`sf-decomposer` supports automatic decomposition and recomposition by defining a `.sfdecomposer.config.json` file in your project root.
 
-To automate decomposing and recomposing before and after `sf` commands, create `.sfdecomposer.config.json` in the root of your Salesforce DX project. You can copy and update the sample [.sfdecomposer.config.json](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/samples/.sfdecomposer.config.json) provided.
+You can copy and update the sample [.sfdecomposer.config.json](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/samples/.sfdecomposer.config.json).
 
-- `metadataSuffixes` is required and should be a comma-separated string of metadata suffixes to decompose automatically after retrievals.
+- `metadataSuffixes` is required and should be a comma-separated string of metadata suffixes to decompose and recompose based on the CLI command.
 - `ignorePackageDirectories` is optional and should be a comma-separated string of package directories to ignore.
-- `prePurge` is optional and should be a boolean. If true, this will delete any existing decomposed files before decomposing the files. If you do not provide this, the default will be `false`. This flag is not used by the recompose command/pre-run hook.
-- `postPurge` is optional and should be a boolean. If true, this will delete the retrieval file after decomposing it or delete the decomposed files after recomposing them. If you do not provide this, the default will be `false`.
-- `decomposedFormat` is optional and should be either `xml`, `json`, `json5`, or `yaml`, depending on what file format you want the decomposed files created as. If you do not provide this, the default will be `xml`.
+- `prePurge` is optional and should be `true` or `false`. If true, this will delete any existing decomposed files before decomposing the files. This defauls to `false`.
+- `postPurge` is optional and should be `true` or `false`. If true, this will delete the retrieval file after decomposing it or delete the decomposed files after recomposing them. This defauls to `false`.
+- `decomposedFormat` is optional and should be either `xml`, `json`, `json5`, or `yaml`, depending on the decomposed file format. This defaults to `xml`.
 
-If `.sfdecomposer.config.json` is found, the hooks will fire:
+If `.sfdecomposer.config.json` is found, the hooks will run:
 
-- the decompose command after a `sf project retrieve start` command completes successfully (post-run)
-- the recompose command before a `sf project deploy [start/validate]` command starts (pre-run)
+- the decompose command **after** a `sf project retrieve start` command completes successfully (post-run)
+- the recompose command **before** a `sf project deploy [start/validate]` command starts (pre-run)
 
 If `.sfdecomposer.config.json` isn't found, the hooks will be skipped.
 
@@ -279,30 +275,37 @@ If `.sfdecomposer.config.json` isn't found, the hooks will be skipped.
 
 The Salesforce CLI **must** ignore the decomposed files and allow the recomposed files.
 
-You can use the sample [.forceignore](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/samples/.forceignore) provided. Update the decomposed file extensions based on what format you're using (`.xml`, `.json`, or `.yaml`).
+You can use the sample [.forceignore](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/samples/.forceignore). Update the decomposed file extensions based on what format you're using (`.xml`, `.json`, `.json5`, or `.yaml`).
 
 ### `.sfdecomposerignore`
 
-If you wish, you can create a `.sfdecomposerignore` file in the root of your Salesforce DX project to ignore specific XMLs when running the decompose command. The `.sfdecomposerignore` file should follow [.gitignore spec 2.22.1](https://git-scm.com/docs/gitignore).
+Optionally, you can create a `.sfdecomposerignore` file in the root of your Salesforce DX project to ignore specific XMLs when decomposing. The `.sfdecomposerignore` file should follow [.gitignore spec 2.22.1](https://git-scm.com/docs/gitignore).
 
-When the decompose command is ran with the `--debug` flag and it processes a file that matches an entry in `.sfdecomposerignore`, a warning will be printed to the `disassemble.log`:
+When you run `sf decomposer decompose --debug` and it processes a file that matches an entry in `.sfdecomposerignore`, a warning will be printed to the `disassemble.log`:
 
 ```
 [2024-05-22T09:32:12.078] [WARN] default - File ignored by .sfdecomposerignore: C:\Users\matth\Documents\sf-decomposer\test\baselines\bots\Assessment_Bot\v1.botVersion-meta.xml
 ```
 
-`.sfdecomposerignore` is not read by the recompose command.
+`.sfdecomposerignore` is not read when recomposing metadata.
 
 ### `.gitignore`
 
 Optionally, git can ignore the recomposed files so you don't stage those in your repositories. You can also have git ignore the `disassemble.log` created by the `xml-disassembler` package.
 
-You can use the sample [.gitignore](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/samples/.gitignore) provided.
+You can use the sample [.gitignore](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/samples/.gitignore).
 
 ## Issues
 
 If you encounter any bugs or would like to request features, please create an [issue](https://github.com/mcarvin8/sf-decomposer/issues).
 
+## Built With
+
+- [`xml-disassembler`](https://github.com/mcarvin8/xml-disassembler)
+- [`xml2json-disassembler`](https://github.com/mcarvin8/xml2json-disassembler)
+- [`xml2yaml-disassembler`](https://github.com/mcarvin8/xml2yaml-disassembler)
+- [`xml2json5-disassembler`](https://github.com/mcarvin8/xml2json5-disassembler)
+
 ## Contributing
 
 Contributions are welcome! See [Contributing](https://github.com/mcarvin8/sf-decomposer/blob/main/CONTRIBUTING.md).

package/oclif.lock

@@ -1500,10 +1500,10 @@
     strip-ansi "6.0.1"
     ts-retry-promise "^0.8.1"
 
-"@salesforce/core@^8.1.1", "@salesforce/core@^8.2.1", "@salesforce/core@^8.2.3", "@salesforce/core@^8.8.3":
-  version "8.8.4"
-  resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-8.8.4.tgz#1995d387a62c48810b4e0a66c68192ccdcf8001f"
-  integrity sha512-TKioMWh/QWmXjnD0bMNvFHEqaH175TCYWNXUCO1CixdhhI0p1MQj4AnQsk8wuRJiH5kVhiYw6Z7NukcIxLtbUw==
+"@salesforce/core@^8.1.1", "@salesforce/core@^8.2.1", "@salesforce/core@^8.2.3", "@salesforce/core@^8.8.5":
+  version "8.8.5"
+  resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-8.8.5.tgz#4004e22523e4e45b42631733d06dc8aec9fdc23d"
+  integrity sha512-eCiiO4NptvKkz04A4ivBVLzEBy/6IIFmaXoZ4tnF1FcD5MESvC+Xuc+0RFSRiYmPi5oloKNl6njrfVCKAho2zQ==
   dependencies:
     "@jsforce/jsforce-node" "^3.6.5"
     "@salesforce/kit" "^3.2.2"
@@ -1596,12 +1596,12 @@
     string-width "^7.2.0"
     terminal-link "^3.0.0"
 
-"@salesforce/source-deploy-retrieve@^12.16.4":
-  version "12.16.4"
-  resolved "https://registry.yarnpkg.com/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-12.16.4.tgz#56f20625bf9e0a51a273b2cb036e9b14fa63fa57"
-  integrity sha512-V7kECbfKE+tk46NjexWPuFHucHJDYg/HLPDTinJq7KTQgrtE4DEzheCEbyh8mku6queZZOaxZe9vlTemasrmGA==
+"@salesforce/source-deploy-retrieve@^12.16.10":
+  version "12.16.10"
+  resolved "https://registry.yarnpkg.com/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-12.16.10.tgz#b38ee71f9e5691212beae6575078ec8459b59a00"
+  integrity sha512-O1K5I5ZmMTfCZ4SV+/w5iWMjGsHSU+PtHCx7gJVcgH8emY25OUhxrQPqb7BS2jupKQZy6U6hhVhkcD9yYqClag==
   dependencies:
-    "@salesforce/core" "^8.8.3"
+    "@salesforce/core" "^8.8.5"
     "@salesforce/kit" "^3.2.3"
     "@salesforce/ts-types" "^2.0.12"
     "@salesforce/types" "^1.3.0"
@@ -1615,7 +1615,7 @@
     mime "2.6.0"
     minimatch "^9.0.5"
     proxy-agent "^6.4.0"
-    yaml "^2.6.1"
+    yaml "^2.7.0"
 
 "@salesforce/ts-types@^2.0.10", "@salesforce/ts-types@^2.0.12":
   version "2.0.12"
@@ -4118,10 +4118,10 @@ fast-xml-parser@^4.5.3:
   dependencies:
     strnum "^1.1.1"
 
-fast-xml-parser@^5.0.8:
-  version "5.0.8"
-  resolved "https://registry.yarnpkg.com/fast-xml-parser/-/fast-xml-parser-5.0.8.tgz#cb84ca077c0c5c45906051c13c4075ed44d3f271"
-  integrity sha512-qY8NiI5L8ff00F2giyICiJxSSKHO52tC36LJqx2JtvGyAd5ZfehC/l4iUVVHpmpIa6sM9N5mneSLHQG2INGoHA==
+fast-xml-parser@^5.0.9:
+  version "5.0.9"
+  resolved "https://registry.yarnpkg.com/fast-xml-parser/-/fast-xml-parser-5.0.9.tgz#5b64c810e70941a9c07b07ead8299841fbb8dd76"
+  integrity sha512-2mBwCiuW3ycKQQ6SOesSB8WeF+fIGb6I/GG5vU5/XEptwFFhp9PE8b9O7fbs2dpq9fXn4ULR3UsfydNUCntf5A==
   dependencies:
     strnum "^2.0.5"
 
@@ -4785,11 +4785,16 @@ ieee754@^1.2.1:
   resolved "https://registry.npmjs.org/ieee754/-/ieee754-1.2.1.tgz"
   integrity sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==
 
-ignore@^5.2.0, ignore@^5.2.4, ignore@^5.3.0, ignore@^5.3.1, ignore@^5.3.2:
+ignore@^5.2.0, ignore@^5.2.4, ignore@^5.3.0, ignore@^5.3.2:
   version "5.3.2"
   resolved "https://registry.yarnpkg.com/ignore/-/ignore-5.3.2.tgz#3cd40e729f3643fd87cb04e50bf0eb722bc596f5"
   integrity sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==
 
+ignore@^7.0.3:
+  version "7.0.3"
+  resolved "https://registry.yarnpkg.com/ignore/-/ignore-7.0.3.tgz#397ef9315dfe0595671eefe8b633fec6943ab733"
+  integrity sha512-bAH5jbK/F3T3Jls4I0SO1hmPR0dKU0a7+SY6n1yzRtG54FLO8d6w/nxLFX2Nb7dBu6cCWXPaAME6cYqFUMmuCA==
+
 immediate@~3.0.5:
   version "3.0.6"
   resolved "https://registry.npmjs.org/immediate/-/immediate-3.0.6.tgz"
@@ -7814,13 +7819,13 @@ write-file-atomic@^3.0.0:
     signal-exit "^3.0.2"
     typedarray-to-buffer "^3.1.5"
 
-xml-disassembler@^1.3.13:
-  version "1.3.13"
-  resolved "https://registry.yarnpkg.com/xml-disassembler/-/xml-disassembler-1.3.13.tgz#fade68d62add9992340b94b6e4537bc040333c87"
-  integrity sha512-qjfNcTNSAXbLDErLw6hlckpm9ARQDQDJ+CMDFPV2LrheMUhlDF3Z4vZKSNBWyTrb+4PgUOTpGXnXRpgFPtcO9Q==
+xml-disassembler@^1.3.15:
+  version "1.3.15"
+  resolved "https://registry.yarnpkg.com/xml-disassembler/-/xml-disassembler-1.3.15.tgz#ddd25995caa311aa7168875d82abb5bad9c89ec1"
+  integrity sha512-YcBJK0HwS70v74q3aU6jMOfEeD8+irzMAI9ImPBxhezZNq6zjxTJg9TNlECDvjpzKMHGuscWoYLhrF9eyMM7eg==
   dependencies:
-    fast-xml-parser "^5.0.8"
-    ignore "^5.3.1"
+    fast-xml-parser "^5.0.9"
+    ignore "^7.0.3"
     log4js "^6.9.1"
     tslib "^2.6.2"
 
@@ -7832,30 +7837,30 @@ xml2js@^0.6.2:
     sax ">=0.6.0"
     xmlbuilder "~11.0.0"
 
-xml2json-disassembler@^1.1.13:
-  version "1.1.13"
-  resolved "https://registry.yarnpkg.com/xml2json-disassembler/-/xml2json-disassembler-1.1.13.tgz#04f8577fda4bbcbf5c167d5320b6ed88e46f75c7"
-  integrity sha512-YWIybFAJ59yiuUbQ+DgeJ/aOd5ACfVquCmZNbMlqJGlqVhON3IUCJ8SPyhfRJwuuJScAbBBbi+kXrhI8KMRz7w==
+xml2json-disassembler@^1.1.14:
+  version "1.1.14"
+  resolved "https://registry.yarnpkg.com/xml2json-disassembler/-/xml2json-disassembler-1.1.14.tgz#d6cbdd6ce8f6f2599294d8aecc70180d28761b4c"
+  integrity sha512-X+UyuqrJHOQFROlLTLe5RtN6Z0Xy/6GhKSclDrQgzpkT2dKSTnILb1KQhcfkEtMLj1IppKtoH7f3ol9wweonDQ==
   dependencies:
     tslib "^2.6.2"
-    xml-disassembler "^1.3.13"
+    xml-disassembler "^1.3.15"
 
-xml2json5-disassembler@^1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/xml2json5-disassembler/-/xml2json5-disassembler-1.0.0.tgz#26c2693038cee332558d98d16abc378b62abf263"
-  integrity sha512-PeNQcVNyLhZ90gG/1bCHSQQ7SYlk7IIYQxgqUOj9Tc27OCjpJ3ZPGidbHZ4HfCjrYQMxrNd6FnozkieVEGTuXw==
+xml2json5-disassembler@^1.0.1:
+  version "1.0.1"
+  resolved "https://registry.yarnpkg.com/xml2json5-disassembler/-/xml2json5-disassembler-1.0.1.tgz#85ca4c7c13e1a0981ce66a0c9193f64380d738ba"
+  integrity sha512-lZmw7SE4rNMFDlpfZXIKFKQqIWMJEu5JH3GubRVVCC1HMHmEZdD0RPfw49JN/PuwVTcTHwWh/EXvIdrrVNLtAQ==
   dependencies:
     json5 "^2.2.3"
     tslib "^2.6.2"
-    xml-disassembler "^1.3.13"
+    xml-disassembler "^1.3.15"
 
-xml2yaml-disassembler@^1.1.13:
-  version "1.1.13"
-  resolved "https://registry.yarnpkg.com/xml2yaml-disassembler/-/xml2yaml-disassembler-1.1.13.tgz#8c524cacce2f6741691e2958c3fab25fa4479195"
-  integrity sha512-itP9OrE77LRNqWbsU0Fs6rJJT59R1k0lqY6+ycm4IZKITMSvnCVFznbCaZ6EUv+GvDZd73+hreO4so6vcqDRDw==
+xml2yaml-disassembler@^1.1.14:
+  version "1.1.14"
+  resolved "https://registry.yarnpkg.com/xml2yaml-disassembler/-/xml2yaml-disassembler-1.1.14.tgz#fe1d732519f4dc14dd8570b741bee338e1e8fabc"
+  integrity sha512-4bfalNt7wXctsrBoh/VJhtCrAIRYCDXiTJeMmzNvEvn2Uffi3R32AjTwWPVXdHqlMV8csNr7bO/riFqy/o67pg==
   dependencies:
     tslib "^2.6.2"
-    xml-disassembler "^1.3.13"
+    xml-disassembler "^1.3.15"
     yaml "^2.7.0"
 
 xmlbuilder@~11.0.0:
@@ -7883,7 +7888,7 @@ yallist@^4.0.0:
   resolved "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz"
   integrity sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==
 
-yaml@^2.4.5, yaml@^2.6.1, yaml@^2.7.0:
+yaml@^2.4.5, yaml@^2.7.0:
   version "2.7.0"
   resolved "https://registry.yarnpkg.com/yaml/-/yaml-2.7.0.tgz#aef9bb617a64c937a9a748803786ad8d3ffe1e98"
   integrity sha512-+hSoy/QHluxmC9kCIJyL/uyFmLmc+e5CFR5Wa+bpIhIj85LVb9ZH2nVnqrHoSvKogwODv0ClqZkmiSSaIH5LTA==

package/oclif.manifest.json

@@ -200,5 +200,5 @@
       ]
     }
   },
-  "version": "5.4.0"
+  "version": "5.4.2"
 }

package/package.json

@@ -1,17 +1,17 @@
 {
   "name": "sf-decomposer",
   "description": "Break down large Salesforce metadata files into smaller, more manageable files for version control and then recreate deployment-compatible files.",
-  "version": "5.4.0",
+  "version": "5.4.2",
   "dependencies": {
     "@oclif/core": "^4",
     "@salesforce/core": "^8.2.1",
     "@salesforce/sf-plugins-core": "^11.2.1",
-    "@salesforce/source-deploy-retrieve": "^12.16.4",
+    "@salesforce/source-deploy-retrieve": "^12.16.10",
     "fs-extra": "^11.2.0",
-    "xml-disassembler": "^1.3.13",
-    "xml2json-disassembler": "^1.1.13",
-    "xml2json5-disassembler": "^1.0.0",
-    "xml2yaml-disassembler": "^1.1.13"
+    "xml-disassembler": "^1.3.15",
+    "xml2json-disassembler": "^1.1.14",
+    "xml2json5-disassembler": "^1.0.1",
+    "xml2yaml-disassembler": "^1.1.14"
   },
   "devDependencies": {
     "@commitlint/cli": "^18.6.1",
@@ -51,6 +51,7 @@
     "xml",
     "yaml",
     "json",
+    "json5",
     "decompose",
     "reassemble",
     "recompose",