How is a JavaScript translation dictionary («js-translation.json») generated on the static assets deployment («bin/magento setup:static-content:deploy»)?

static-content
localization
asset
js-translation-json
static-content-deploy

(Dmitry Fedyuk) #1

1. Magento\Setup\Console\Command\DeployStaticContentCommand::execute()

Context:

2. Magento\Deploy\Service\DeployStaticContent::deploy()

Context:

3. Magento\Deploy\Service\DeployTranslationsDictionary::deploy()

Context:

4. Magento\Framework\App\State::emulateAreaCode()

Context:

5. Magento\Deploy\Service\DeployTranslationsDictionary::deploy()

Context:

6. Magento\Deploy\Service\DeployStaticFile::deployFile()

Context:

7. Magento\Framework\App\View\Asset\Publisher::publish()

Context:

8. Magento\Framework\App\View\Asset\Publisher::publishAsset()

Context:

9. Magento\Framework\View\Asset\File::getSourceFile()

Context:

10. Magento\Framework\View\Asset\Source::getFile()

Context:

11. Magento\Framework\View\Asset\Source::preProcess()

Context:

12. Magento\Framework\View\Asset\PreProcessor\Pool::process()


Context:

13. Magento\Translation\Model\Json\PreProcessor::process()

Context:

14. Magento\Translation\Model\Js\DataProvider::getData()


How is js-translation.json file generated?
(Dmitry Fedyuk) #2

The previous analysis (written 2 years ago): How is js-translation.json file generated?

See also: