2.2.4 to 2.2.5 js-translation.json gets messed up

[cscarfo]

I upgraded from 2.2.4 to 2.2.5 with language IT_IT set for back- and frontend.
I did it several times, from the wizard and CLI, following all instructions carefully.
Both ways I got many back and frontend text messages, tips, etc. messed up, enclosed in curly braces and repeated. Below you find a sample of it.
Finally I got down to the problem: the js-translation.json files in pub/static/adminhtml/Magento/backend/it_IT and its counterpart in the frontend had grown from 15,7 KB to 53,1 KB and from 3,0 KB to 67,6 KB respectively after the upgrade.
I replaced them with the 2.2.4 versions and everything returned as normal.
Here a sample form the 2.2.4 and from the 2.2.5 backend js-translation.json:
2.2.4:
{"Please enter {0} words or less.":"Inserisci {0} parole o meno.","Please enter at least {0} words.":"Inserisci almeno {0} parole.","Please enter between {0} and {1} words.":"Inserisci un numero di parole tra {0} e {1}.","Letters or punctuation only please":"Solo lettere o segni di punteggiatura","Letters, numbers, spaces or underscores only please":"Solo lettere, numeri, spazi e underscore","Letters only please":"Solo lettere","No white space please":"Nessuno spazio bianco","Your ZIP-code must be in the range 902xx-xxxx to 905-xx-xxxx":"Il tuo codice postale deve essere nell'intervallo 902xx-xxxx a 905-xx-xxxx","A positive or negative non-decimal number please":"Inserisci un numero positivo o negativo non decimale","The specified vehicle identification number (VIN) is invalid.":"Il numero di identificazione specificato del veicolo (VIN) non \u00e8 valido."

2.2.5
{"All ":"{{{All }}{{All }}{{All }}{{themeMagento/backend}}}","more":"{{{more}}{{more}}{{more}}{{themeMagento/backend}}}","Please enter {0} words or less.":"{{{Inserisci {0} parole o meno.}}{{Inserisci {0} parole o meno.}}{{Please enter {0} words or less.}}{{themeMagento/backend}}}","Please enter at least {0} words.":"{{{Inserisci almeno {0} parole.}}{{Inserisci almeno {0} parole.}}{{Please enter at least {0} words.}}{{themeMagento/backend}}}","Please enter between {0} and {1} words.":"{{{Inserisci un numero di parole tra {0} e {1}.}}{{Inserisci un numero di parole tra {0} e {1}.}}{{Please enter between {0} and {1} words.}}{{themeMagento/backend}}}","Letters or punctuation only please":"{{{Solo lettere o segni di punteggiatura}}{{Solo lettere o segni di punteggiatura}}{{Letters or punctuation only please}}{{themeMagento/backend}}}","Letters, numbers, spaces or underscores only please":"{{{Solo lettere, numeri, spazi e underscore}}{{Solo lettere, numeri, spazi e underscore}}{{Letters, numbers, spaces or underscores only please}}{{themeMagento/backend}}}","Letters only please":"{{{Solo lettere}}{{Solo lettere}}{{Letters only please}}{{themeMagento/backend}}}","No white space please":"{{{Nessuno spazio bianco}}{{Nessuno spazio bianco}}{{No white space please}}{{themeMagento/backend}}}","Your ZIP-code must be in the range 902xx-xxxx to 905-xx-xxxx":"{{{Il tuo codice postale deve essere nell'intervallo 902xx-xxxx a 905-xx-xxxx}}{{Il tuo codice postale deve essere nell'intervallo 902xx-xxxx a 905-xx-xxxx}}{{Your ZIP-code must be in the range 902xx-xxxx to 905-xx-xxxx}}{{themeMagento/backend}}}","A positive or negative non-decimal number please":"{{{Inserisci un numero positivo o negativo non decimale}}{{Inserisci un numero positivo o negativo non decimale}}{{A positive or negative non-decimal number please}}{{themeMagento/backend}}}","The specified vehicle identification number (VIN) is invalid.":"{{{Il numero di identificazione specificato del veicolo (VIN) non \u00e8 valido.}}{{Il numero di identificazione specificato del veicolo (VIN) non \u00e8 valido.}}{{The specified vehicle identification number (VIN) is invalid.}}

Thanks

P.S. The date fields in the catalog page now work as expected

[magento-engcom-team]

Hi @cscarfo. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me {$VERSION} instance

where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.

@cscarfo do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[engcom-backlog-nickolas]

@cscarfo, thank you for your report.
Please use the issue reporting guidelines to report an issue. Please, edit issue description and include the preconditions, the steps required to reproduce, the actual result, and the expected result.
Please, add the following information:

• Preconditions: Magento version
• Steps to reproduce
• Expected result
• Actual result

[engcom-backlog-nickolas]

@cscarfo, we are closing this issue due to inactivity. If you'd like to update it, please reopen the issue.

[steffen-wirth]

hi @engcom-backlog-nickolas ,
i experiencing the same after the upgrade from 2.1.6 to 2.2.6
if i use the production mode, the created js-translation.json files (cli command bin/magento se:st:de fr_FR de_CH en_US) are broken - not correct brackets
if i use the development mode and let the page request handle the creation, the files seem to be ok

seems the issue is the cli command creation
pls open the issue and investigate this further

UPDATE:
after few more tries and enabling the production mode again - strangly - the problem disappeared