@hyper.software/visitor-common-translations 2.0.82 → 2.0.84

package/README.md

@@ -1,93 +1,93 @@
-# vz-common-translations
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.com/vz-web/vz-common-translations.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.com/vz-web/vz-common-translations/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+# vz-common-translations
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://gitlab.com/vz-web/vz-common-translations.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](https://gitlab.com/vz-web/vz-common-translations/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

package/lib/translations/locale/locale.de-DE.json

@@ -46,6 +46,9 @@
     "App.admin.bookings.receipt.iban": "IBAN",
     "App.admin.bookings.receipt.itemDescription": "Bezeichnung",
     "App.admin.bookings.receipt.notes": "Anmerkung",
+    "App.admin.bookings.receipt.paymentMethod": "Bezahlverfahren",
+    "App.admin.bookings.receipt.paymentMethod.CARD": "Karte",
+    "App.admin.bookings.receipt.paymentMethod.CASH": "Kasse",
     "App.admin.bookings.receipt.quantity": "Anzahl",
     "App.admin.bookings.receipt.rate": "Preis",
     "App.admin.bookings.receipt.receipt": "Rechnung",
@@ -1624,6 +1627,7 @@
     "App.whatsApp.support.link": "WhatsApp öffnen",
     "App.whatsApp.support.subtitle": "QR-Code Scannen um den Chat mit Visitor auf Ihrem Handy zu öffnen",
     "any.api.validation.INVALID_TYPE.locationDescription": "Ein unbekannter Fehler ist aufgetreten, bitte wenden sie sich an den Visitor Support",
+    "any.api.validation.general.error": "Ein unbekannter Fehler ist aufgetreten, bitte wenden sie sich an den Visitor Support.",
     "backendApiClient.unknownError": "Ein unerwarteter Fehler ist aufgetreten. Unser Personal wurde benachrichtigt und arbeitet an einer Lösung.",
     "main.api.bookings.cannotSync.noRoomAvailable.createBooking": "Buchung kann nicht erstellt werden, da einige der Zimmer nicht mehr verfügbar sind",
     "main.api.bookings.cannotSync.noRoomAvailable.importBookings": "Kann nicht synchronisiert werden, da diese Buchung sich mit einer anderen im selben Zimmer überschneidet",

package/lib/translations/locale/locale.en-US.json

@@ -46,6 +46,9 @@
     "App.admin.bookings.receipt.iban": "Iban",
     "App.admin.bookings.receipt.itemDescription": "Item description",
     "App.admin.bookings.receipt.notes": "Here you can add some notes",
+    "App.admin.bookings.receipt.paymentMethod": "Payment method",
+    "App.admin.bookings.receipt.paymentMethod.CARD": "Card",
+    "App.admin.bookings.receipt.paymentMethod.CASH": "Cash",
     "App.admin.bookings.receipt.quantity": "Quantity",
     "App.admin.bookings.receipt.rate": "Rate",
     "App.admin.bookings.receipt.receipt": "Receipt",
@@ -1624,6 +1627,7 @@
     "App.whatsApp.support.link": "Open WhatsApp",
     "App.whatsApp.support.subtitle": "Scan the QR code or click the button to go directly to the chat with Visitor.",
     "any.api.validation.INVALID_TYPE.locationDescription": "An unexpected error has occured. Please contact Visitor support.",
+    "any.api.validation.general.error": "An unexpected error has occured. Please contact Visitor support.",
     "backendApiClient.unknownError": "An unexpected error has occurred. Our staff has been notified and is working on a fix.",
     "main.api.bookings.cannotSync.noRoomAvailable.createBooking": "Cannot create the booking because some of the rooms are no longer available",
     "main.api.bookings.cannotSync.noRoomAvailable.importBookings": "Cannot import the bookings because some of them overlap.",

package/lib/translations/locale/locale.es-ES.json

@@ -46,6 +46,9 @@
     "App.admin.bookings.receipt.iban": "Iban",
     "App.admin.bookings.receipt.itemDescription": "Descripción del artículo",
     "App.admin.bookings.receipt.notes": "Aquí puedes agregar algunas notas",
+    "App.admin.bookings.receipt.paymentMethod": "Método de pago",
+    "App.admin.bookings.receipt.paymentMethod.CARD": "Tarjeta",
+    "App.admin.bookings.receipt.paymentMethod.CASH": "Dinero",
     "App.admin.bookings.receipt.quantity": "Cantidad",
     "App.admin.bookings.receipt.rate": "Tarifa",
     "App.admin.bookings.receipt.receipt": "Recibo",
@@ -1624,6 +1627,7 @@
     "App.whatsApp.support.link": "Abre Wharsapp",
     "App.whatsApp.support.subtitle": "Escanee el código QR o haga clic en el botón para ir directamente al chat con el Visitor.",
     "any.api.validation.INVALID_TYPE.locationDescription": "Se ha producido un error inesperado. Póngase en contacto con el servicio de asistencia al Visitor.",
+    "any.api.validation.general.error": "Se ha producido un error inesperado. Póngase en contacto con el servicio de asistencia al Visitor.",
     "backendApiClient.unknownError": "Se ha producido un error inesperado. Nuestro equipo ha sido notificado y está trabajando en una solución.",
     "main.api.bookings.cannotSync.noRoomAvailable.createBooking": "No se puede crear la reserva porque algunas de las habitaciones ya no están disponibles",
     "main.api.bookings.cannotSync.noRoomAvailable.importBookings": "No se pueden importar las reservas porque algunas de ellas se superponen",

package/lib/translations/locale/locale.fr-FR.json

@@ -46,6 +46,9 @@
     "App.admin.bookings.receipt.iban": "Iban",
     "App.admin.bookings.receipt.itemDescription": "Description de l'article",
     "App.admin.bookings.receipt.notes": "Ici, vous pouvez ajouter quelques notes",
+    "App.admin.bookings.receipt.paymentMethod": "Mode de paiement",
+    "App.admin.bookings.receipt.paymentMethod.CARD": "Carte",
+    "App.admin.bookings.receipt.paymentMethod.CASH": "Espèces",
     "App.admin.bookings.receipt.quantity": "Quantité",
     "App.admin.bookings.receipt.rate": "Tarif",
     "App.admin.bookings.receipt.receipt": "Reçu",
@@ -1624,6 +1627,7 @@
     "App.whatsApp.support.link": "Ouvrir WhatsApp",
     "App.whatsApp.support.subtitle": "Scannez le code QR ou cliquez sur le bouton pour accéder directement au chat avec le visiteur.",
     "any.api.validation.INVALID_TYPE.locationDescription": "Une erreur inattendue s'est produite. Veuillez contacter l'assistance aux visiteurs.",
+    "any.api.validation.general.error": "Une erreur inattendue s'est produite. Veuillez contacter l'assistance aux visiteurs.",
     "backendApiClient.unknownError": "Une erreur inattendue s'est produite. Notre équipe a été informée et travaille sur une solution.",
     "main.api.bookings.cannotSync.noRoomAvailable.createBooking": "Impossible de créer la réservation car certaines chambres ne sont plus disponibles",
     "main.api.bookings.cannotSync.noRoomAvailable.importBookings": "Impossible d'importer les réservations car certaines d'entre elles se chevauchent.",

package/lib/translations/locale/locale.it-IT.json

@@ -46,6 +46,9 @@
     "App.admin.bookings.receipt.iban": "Iban",
     "App.admin.bookings.receipt.itemDescription": "Descrizione articolo",
     "App.admin.bookings.receipt.notes": "Qui puoi aggiungere alcune note",
+    "App.admin.bookings.receipt.paymentMethod": "Metodo di pagamento",
+    "App.admin.bookings.receipt.paymentMethod.CARD": "Carta",
+    "App.admin.bookings.receipt.paymentMethod.CASH": "Contanti",
     "App.admin.bookings.receipt.quantity": "Quantità",
     "App.admin.bookings.receipt.rate": "Tariffa",
     "App.admin.bookings.receipt.receipt": "Ricevuta",
@@ -1624,6 +1627,7 @@
     "App.whatsApp.support.link": "Apri WhatsApp",
     "App.whatsApp.support.subtitle": "Scansiona il codice QR o clicca il pulsante per andare direttamente alla chat con il Visitatore.",
     "any.api.validation.INVALID_TYPE.locationDescription": "Si è verificato un errore imprevisto. Contatta l'assistenza per i visitatori.",
+    "any.api.validation.general.error": "Si è verificato un errore imprevisto. Contatta l'assistenza per i visitatori.",
     "backendApiClient.unknownError": "Si è verificato un errore imprevisto. Il nostro personale è stato informato e sta lavorando per risolvere il problema.",
     "main.api.bookings.cannotSync.noRoomAvailable.createBooking": "Impossibile creare la prenotazione perché alcune camere non sono più disponibili",
     "main.api.bookings.cannotSync.noRoomAvailable.importBookings": "Impossibile importare le prenotazioni perché alcune di esse si sovrappongono.",

package/lib/translations/locale/locale.ro-RO.json

@@ -46,6 +46,9 @@
     "App.admin.bookings.receipt.iban": "IBAN",
     "App.admin.bookings.receipt.itemDescription": "Descrierea obiectului",
     "App.admin.bookings.receipt.notes": "Aici puteți adăuga niște note",
+    "App.admin.bookings.receipt.paymentMethod": "Modalitate de plată",
+    "App.admin.bookings.receipt.paymentMethod.CARD": "Card",
+    "App.admin.bookings.receipt.paymentMethod.CASH": "Numerar",
     "App.admin.bookings.receipt.quantity": "Cantitate",
     "App.admin.bookings.receipt.rate": "Rata",
     "App.admin.bookings.receipt.receipt": "Chitanța",
@@ -1623,7 +1626,8 @@
     "App.whatsApp.support": "Chat WhatsApp",
     "App.whatsApp.support.link": "Deschideți WhatsApp",
     "App.whatsApp.support.subtitle": "Scanați codul QR sau apăsați butonul pentru a merge direct la chat-ul cu vizitatorul.",
-    "any.api.validation.INVALID_TYPE.locationDescription": "A apărut o eroare neașteptată. Vă rugăm să contactați suportul pentru vizitatori.",
+    "any.api.validation.INVALID_TYPE.locationDescription": "A apărut o eroare neașteptată. Vă rugăm să contactați suportul Visitor.",
+    "any.api.validation.general.error": "A apărut o eroare neașteptată. Vă rugăm să contactați suportul Visitor.",
     "backendApiClient.unknownError": "A apărut o eroare neașteptată. Personalul nostru a fost notificat și lucrează la rezolvarea problemei.",
     "main.api.bookings.cannotSync.noRoomAvailable.createBooking": "Nu se poate crea rezervarea pentru că unele dintre camere nu mai sunt disponibile",
     "main.api.bookings.cannotSync.noRoomAvailable.importBookings": "Nu se pot importa rezervările pentru că unele dintre ele se suprapun.",

package/package.json

@@ -1,70 +1,70 @@
-{
-  "name": "@hyper.software/visitor-common-translations",
-  "version": "2.0.82",
-  "author": "Hyper Software <tomescu.raul+hyper@gmail.com>",
-  "description": "Visitor Common Translations",
-  "main": "lib/index.js",
-  "types": "./lib/index.d.ts",
-  "engines": {
-    "node": ">= 18.18.0"
-  },
-  "files": [
-    "lib",
-    "es"
-  ],
-  "keywords": [
-    "Javascript",
-    "translations"
-  ],
-  "repository": {},
-  "license": "ISC",
-  "bugs": {},
-  "scripts": {
-    "test": "jest --watch --runInBand",
-    "test.coverage": "jest --coverage",
-    "lint": "eslint src --ext .ts,.tsx",
-    "format": "prettier-eslint \"src/**/*.ts\" \"src/**/*.tsx\" --write",
-    "build": "tsc",
-    "publish-package": "yarn translations-fix && git add . && git commit -m 'Pre-publish package' --allow-empty && rm -rf ./lib && yarn tsc && npm version patch && npm publish && git add . && git commit -m 'Post-publish package' --allow-empty && git push"
-  },
-  "husky": {
-    "hooks": {
-      "pre-commit": "tsc && npm run lint && npm run format"
-    }
-  },
-  "dependencies": {
-    "intl-format-cache": "^4.3.1",
-    "intl-messageformat": "^10.5.4",
-    "library-name": "^1.1.0"
-  },
-  "devDependencies": {
-    "@types/jest": "^29.5.7",
-    "@types/node": "^20.8.10",
-    "cross-env": "^7.0.3",
-    "er-translations-fix": "^1.0.7",
-    "identity-obj-proxy": "^3.0.0",
-    "in-publish": "^2.0.1",
-    "jest": "^29.7.0",
-    "prettier": "^3.0.3",
-    "rimraf": "^5.0.5",
-    "typescript": "^5.2.2"
-  },
-  "jest": {
-    "transform": {
-      ".*": "<rootDir>/jest-preprocessor.js"
-    },
-    "testRegex": "(/__tests__/.*\\.(test|spec))\\.(ts|js)$",
-    "modulePaths": [
-      "./src"
-    ],
-    "moduleFileExtensions": [
-      "js",
-      "json",
-      "ts"
-    ],
-    "moduleDirectories": [
-      "node_modules",
-      "src"
-    ]
-  }
-}
+{
+  "name": "@hyper.software/visitor-common-translations",
+  "version": "2.0.84",
+  "author": "Hyper Software <tomescu.raul+hyper@gmail.com>",
+  "description": "Visitor Common Translations",
+  "main": "lib/index.js",
+  "types": "./lib/index.d.ts",
+  "engines": {
+    "node": ">= 18.18.0"
+  },
+  "files": [
+    "lib",
+    "es"
+  ],
+  "keywords": [
+    "Javascript",
+    "translations"
+  ],
+  "repository": {},
+  "license": "ISC",
+  "bugs": {},
+  "scripts": {
+    "test": "jest --watch --runInBand",
+    "test.coverage": "jest --coverage",
+    "lint": "eslint src --ext .ts,.tsx",
+    "format": "prettier-eslint \"src/**/*.ts\" \"src/**/*.tsx\" --write",
+    "build": "tsc",
+    "publish-package": "yarn translations-fix && git add . && git commit -m 'Pre-publish package' --allow-empty && rm -rf ./lib && yarn tsc && npm version patch && npm publish && git add . && git commit -m 'Post-publish package' --allow-empty && git push"
+  },
+  "husky": {
+    "hooks": {
+      "pre-commit": "tsc && npm run lint && npm run format"
+    }
+  },
+  "dependencies": {
+    "intl-format-cache": "^4.3.1",
+    "intl-messageformat": "^10.5.4",
+    "library-name": "^1.1.0"
+  },
+  "devDependencies": {
+    "@types/jest": "^29.5.7",
+    "@types/node": "^20.8.10",
+    "cross-env": "^7.0.3",
+    "er-translations-fix": "^1.0.7",
+    "identity-obj-proxy": "^3.0.0",
+    "in-publish": "^2.0.1",
+    "jest": "^29.7.0",
+    "prettier": "^3.0.3",
+    "rimraf": "^5.0.5",
+    "typescript": "^5.2.2"
+  },
+  "jest": {
+    "transform": {
+      ".*": "<rootDir>/jest-preprocessor.js"
+    },
+    "testRegex": "(/__tests__/.*\\.(test|spec))\\.(ts|js)$",
+    "modulePaths": [
+      "./src"
+    ],
+    "moduleFileExtensions": [
+      "js",
+      "json",
+      "ts"
+    ],
+    "moduleDirectories": [
+      "node_modules",
+      "src"
+    ]
+  }
+}