You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create and fill in .env file following .env.example file
Run npm install at the root folder
Start in DEV env: npm run start
Build: npm run build
Start in PROD env:npm run serve
Rules of naming localization files
File names for localization are given by the name of the page, for example personal-info for '/user-account/dashboard/personal-info'.
If the pages are small, you should combine them into one file, for example auth for sign-in, sign-up and auth-verify.
If you will use component on several places of app add the localization of the components to the file common.json/components or to the file with the current page if the component will be used only there.
We add localization for public routes to public.json.
After adding a new file with localization, you need to import it into index.ts for the correct definition of types. ua, en
Localization files consist of nested objects with keys written in camel case.
