Compress the embedded config jsons

[psyirius]

Title

Compress the embedded config jsons

Type of Change

• Releng Optimization

Description

Compress the config json embedding in the final build artifact

Impact

Reduces artifact size resulting in less traffic when fetching.

Checklist

• My code adheres to the coding and style guidelines of the project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no errors/warnings/merge conflicts.

[psyirius]

WARNING

This will mess up the readability of the final build artifact.

If concerned about readability don't merge this!

[Marterich]

Another Idea, if we are going the way of reducing the filesize and ignoring readability you could also think about adding a function like the following example to remove all Powershell Comments from the final compiled file.
This will remove an additional ~2k lines and therefore around 50-60kb

function Remove-PSComments {
    param (
        [string]$FilePath
    )
    if (-not (Test-Path $FilePath)) {
        throw "File '$FilePath' does not exist."
    }
    $content = Get-Content $FilePath -Raw
    # Remove block comments: <# ... #>
    $content = [regex]::Replace($content, '<#.*?#>', '', [System.Text.RegularExpressions.RegexOptions]::Singleline)
    # Remove line comments: # ...
    $content = [regex]::Replace($content, '(^|\s)#.*', '$1')
    # Remove empty lines (lines containing only whitespace or nothing)
    $content = [regex]::Replace($content, '^\s*[\r\n]+', '', [System.Text.RegularExpressions.RegexOptions]::Multiline)
    return $content
}
# Example usage:
Remove-PSComments -FilePath "winutil.ps1" | Set-Content "winutil_minified.ps1"

[psyirius]

I have a feeling that it might not align with the vision of the project!
Closing it!