de-DE and it-IT are loaded by default after replacing them with new values in a multistore setup

[antonioglass]

Current behavior

In order to set up a multistore I edited config (local.json). I replaced all values related to DE and IT with new values but when the app is being built, it still loads the DE and IT languages:

Writing JSON file fallback: en-US.json
Writing JSON file: de-DE.json
Writing JSON file: it-IT.json
Writing JSON file: et-EE.json
Writing JSON file: ru-RU.json

Expected behavior

Only the languages that are specified in the config must be loaded and shown on the website language selector.

Steps to reproduce the issue

1. Set "multistore" to "true";
2. Replace all "de" values with "ee", and all "it" values with "ru", "de-DE" with "et-EE" and "it-IT" with "ru-RU"
3. Run yarn dev / build

Version of Vue Storefront

• Vue Storefront
• Vue Storefront Next

Can you handle fixing this bug by yourself?

• YES
• NO

Which Release Cycle state this refers to? Info for developer. (doesn't apply to Next)

Pick one option.

• This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
• This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
• This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

• Browser: Chrome for Mac Version 91.0.4472.114 (Official Build) (arm64)
• OS: Ubuntu 20.04
• Node: v12.20.0
• Code Version: v1.12.2

Additional information

I noticed, if I do not edit the first "de" and the first "it", the languages are loaded correctly. However, the front end is broken then.

[antonioglass]

Issue resolved by removing default.json from config folder