NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #1609 most downloaded on Packagist
A pretty nice way to expose your translation messages to your JavaScript.
Latest stable
8.0.0
Last release 9 months ago
24 Feb 2026
Release timing varies
gaps range from 5 weeks to 1.9 years
Most releases are documented
notes for 38 of 52 stable releases
Nothing withdrawn
no release was ever pulled
14 years old
56 releases · first in 2012
Drag across the ruler to compare, or tap a release to open it.
Make the bundle configuration compatible with using ENV variables by @kick-the-bucket in #365
Full Changelog: 7.0.0...8.0.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Full Changelog: https://github.com/willdurand/BazingaJsTranslationBundle/compare/7.0.0...8.0.0
Remove usage of the deprecated base extension from HttpKernel by @stof in #360
Full Changelog: 6.1.0...7.0.0
Full Changelog: https://github.com/willdurand/BazingaJsTranslationBundle/compare/6.1.0...7.0.0
Use the UMD build of intl-messageformat in the testsuite by @stof in #361
Thanks @karion @tacman and @stof for helping this release.
Full Changelog: 6.0.0...6.1.0
Thanks @karion @tacman and @stof for helping this release.
Full Changelog: https://github.com/willdurand/BazingaJsTranslationBundle/compare/6.0.0...6.1.0
Add support for Symfony 7 by @stof in https://github.com/willdurand/BazingaJsTranslationBundle/pull/348
Full Changelog: https://github.com/willdurand/BazingaJsTranslationBundle/compare/5.1.0...6.0.0
Fix deprecations of Symfony 6.3 by @stof in https://github.com/willdurand/BazingaJsTranslationBundle/pull/343
Full Changelog: https://github.com/willdurand/BazingaJsTranslationBundle/compare/5.0.0...5.1.0
Fix using HTML tags in ICU messages (#310) by @sustmi in https://github.com/willdurand/BazingaJsTranslationBundle/pull/325
Full Changelog: https://github.com/willdurand/BazingaJsTranslationBundle/compare/4.0.2...5.0.0
Fixed: Fixed: Fix get_message on intl_icu if domain is undefined ( #314 ) - Thanks @spras Fixed: Prevent translation files overwriting files from addR
Fixed: Check the commonJS before AMD dependency for intl-messageformat ( #304 ) - Thanks @ChristianVermeulen
Fixed: Check the commonJS before AMD dependency for intl-messageformat (#304) - Thanks @ChristianVermeulen
Added: Support for Composer 2.0 ( #282 ) - Thanks @blankse Added: Support for ICU-based message formatting ( #288 ) - Thanks @Kocal Removed: support f
Added: Support for Composer 2.0 (#282) - Thanks @blankse
Added: Support for ICU-based message formatting (#288) - Thanks @Kocal
Removed: support for Symfony < 3.3 constructor signature (#214) - Thanks @pierredup
Fixed: All Travis tests, dropping officially the support of Symfony 3.4 (#296, #300) - Thanks @craigh
Added: Support for Composer 2.0 (https://github.com/willdurand/BazingaJsTranslationBundle/pull/282) - Thanks @blankse Added: Support for ICU-based message formatting (https://github.com/willdurand/BazingaJsTranslationBundle/pull/288) - Thanks @Kocal Removed: support for Symfony < 3.3 constructor signature (#214) - Thanks @pierredup Fixed: All Travis tests, dropping officially the support of Symfony 3.4 (#296, #300) - Thanks @craigh
Fix: Return value of "Bazinga\Bundle\JsTranslationBundle\Command\DumpCommand::execute()" must be of the type int, NULL returned, to support Symfony 5
Documentation fix (#262) - Thanks to @bocharsky-bw
Fix: IE bug related to $0 in target placeholder value
Fix: IE bug related to $0 in target placeholder value (#207)
Fix: replace phantom.args by system.args to run the latest version of phantomJS (#215)
Fix: Register command manually to avoid warning in Symfony 3.4 (#220)
Drop PHP 5.3 Support (#218)
Added: Symfony 4 support (#224)
Build URL for specific locales with Symfony Router (#234)
Remove templating dependency (#213)
Remove container injection (#221)
Added: Decrease the size of generated translation and config files
Fix: translator.min.js had syntax errors when in strict mode
Fix: Language fallback in locales with region
Fix: Return default locale if none is found in the Javascript library
Fix: Support for server side rendering using NodeJS
npm run build command inside Resources/ to minify the translator.js file.Added: Support for framework.translator.paths configuration (more information in http://symfony.com/doc/2.8/translation.html)
framework.translator.paths configuration (more information in http://symfony.com/doc/2.8/translation.html)--format and --merge-domains options to bazinga:js-translation:dump command:
--format allows you to specify which formats must be included in the output--merge-domains when set will generate only one file per locale with all the domains in itTranslationFinder. Every translation file is fetched from the Symfony's FrameworkBundle.Nothing published for this version
Added: Widen TranslationFinder::getLocations() visibility to use is in an inheritant class
TranslationFinder::getLocations() visibility to use is in an inheritant classbazinga_jstranslation_jsFixed: Replace string casting on ConfigCache instance with getPath() to omit deprecated warning
ConfigCache instance with getPath() to omit deprecated warningValidator classname with Validation to omit deprecated warningFixed: replaced routing deprecated arguments
Fixed: documentation (change the doc to let composer guess the version constraint)
Added: allow to set expiration time for translations
Fixed: allow all sort of locales (see #119)
Fixed: allow all sort of locales (see #119)
Fixed: better locale filtering
Fixed: better locale filtering
Added: docs for Angular integration
This is a security release. All users MUST upgrade to this release to prevent two potential security issues:
This is a security release. All users MUST upgrade to this release to prevent two potential security issues:
These two security issues have been reported by Andreas Forsblom. THANKS!
Below is the original report Andreas sent me:
Hi William,
First, thank you for a very useful bundle :)
Unfortunately, while investigating if a Symfony project I'm working on was vulnerable to the recent translation-related Symfony security issue (CVE-2014-4931), fixed in Symfony 2.5.2, I discovered that JsTranslationBundle seems to be vulnerable to a unrelated path traversal attack, and potentially also a js injection attack.
---
If I try to retrieve the translations using the following url:
http://localhost/translations?locales=randomstring/something
the file something.js gets created in the subdirectory messages.randomstring of the cache directory:
/var/www/someproject/app/cache/dev/bazinga-js-translation/messages.randomstring/something.js
(this is the actual string that gets passed to the constructor of ConfigCache by the JsTranslationBundle controller)
I can now traverse down from the JsTranslationBundle cache directory (without first creating the "messages.randomstring" directory using the previous step, this won't work):
http://localhost/translations?locales=randomstring/../../evil
becomes
/var/www/someproject/app/cache/dev/bazinga-js-translation/messages.randomstring/../../evil.js
... and depending on the configuration of the server, I could also do
http://localhost/translations?locales=randomstring/../../../../../web/evil
=>
/var/www/someproject/app/cache/dev/bazinga-js-translation/messages.randomstring/../../../../../web/evil.js
thus creating the file evil.js (and evil.js.meta) under the Symfony web root. Depending on file system permissions, this will also overwrite existing files.
---
Again depending on the server configuration, it also seems to be possible to inject actual JavaScript code:
http://localhost/translations?locales=foo%0Auncommented%20code;
=>
(function (Translator) {
Translator.fallback = 'en';
Translator.defaultDomain = 'messages';
// foo
uncommented code;
})(Translator);
This works on some systems I tried, but not others. I suspect it might be related to the character set configuration, but I haven't investigated it further yet.
---
I did my testing using JsTranslationBundle 2.1.0 and Symfony 2.5.2.
Since this is a security issue, I didn't want to submit a pull request or use the GitHub issue tracker.
Three commits fixed these issues: df6c0fd603c0192ebc5584991a52a1092c5f60bd, 7accee93569c3f3d2379f035a41ece66522801fc, and 6ee06b9e974b9b768544fbbd6e1432773d205ebd.
You will find three patch files below in case you can't easily upgrade to this release.
locale parameterAdded: retry on locale fallback in case of locale exists but not the domain
es5-shim and transChoice in MSIE8pt-BR lang attributeArray.prototype methodsImportant: This bundle is now tested against PHP 5.4, 5.5, and 5.6. No effort will be made to keep the code "5.3 compliant".
Thanks to all contributors!
After having released four pre-release versions (2.0.0-alpha1, 2.0.0-alpha2, 2.0.0-alpha3, and 2.0.0-alpha4), the first new stable major version, aka
After having released four pre-release versions (2.0.0-alpha1, 2.0.0-alpha2, 2.0.0-alpha3, and 2.0.0-alpha4), the first new stable major version, aka 2.0.0, is released!
You will find all the details in the different pre-release descriptions linked above. Don't forget to read the bundled UPGRADE file. The documentation is up to date too.
:ship: :star: :stars: :star2: :tada: :boom: :cake: :candy:
Thanks!
The package name has been renamed from willdurand/expose-translation-bundle to willdurand/js-translation-bundle. This release "replaces" the old packa
The package name has been renamed from willdurand/expose-translation-bundle to willdurand/js-translation-bundle. This release "replaces" the old package with the new one.
Changed: the dump command now generates files in web/js/ by default
dump command now generates files in web/js/ by default (#84)Fixed: preserve translation ids that are numeric values
This bundle has been rewritten (75%), and it has led to a new major release. Nothing is backward compatible, and nothing has been done to ease compati
This bundle has been rewritten (75%), and it has led to a new major release. Nothing is backward compatible, and nothing has been done to ease compatibility between the two versions (1.x and 2.x). This bundle has been created three years ago, and it was time to refactor it. I am sorry for this BC break, sincerely.
This new version fixes a bunch of limitations, and potential bugs.
Upgrading from 1.x to 2.x is highly recommended. This requires a few changed (mostly naming changes) but also an update of your JavaScript code as the JS Translator has changed too. Everything should is documented in this UPGRADE file.
Important: it is worth mentioning that it requires at least Symfony 2.3 and above.
Thank you, William.
Fixed: Symfony 2.1 is now supported again
The package name has been renamed from willdurand/expose-translation-bundle to willdurand/js-translation-bundle. This release "replaces" the old packa
The package name has been renamed from willdurand/expose-translation-bundle to willdurand/js-translation-bundle. This release "replaces" the old package with the new one.
Fixed: TranslationFinder to mimic FrameworkBundle's way to find translation files
The package name has been renamed from willdurand/expose-translation-bundle to willdurand/js-translation-bundle. This release "replaces" the old packa
The package name has been renamed from willdurand/expose-translation-bundle to willdurand/js-translation-bundle. This release "replaces" the old package with the new one.
Fixed Translator when multiple locale are loaded with dumped JS
Changed: visibility of TranslationDumper::getTranslationMessages() is now protected.
TranslationDumper::getTranslationMessages() is now protected.The package name has been renamed from willdurand/expose-translation-bundle to willdurand/js-translation-bundle. This release "replaces" the old packa
The package name has been renamed from willdurand/expose-translation-bundle to willdurand/js-translation-bundle. This release "replaces" the old package with the new one.
Fixed: XLIFF dumping (#67, #68)
Removes duplicates from dumped translation messages. See #71
Removes duplicates from dumped translation messages. See #71
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.