FrontEnd documentation updates (OriginProtocol#942)

* Updated the 'Troubleshooting' section to include an error related to the 'Puppeteer' package

* Front-end setup update

shop/README.md

@@ -111,3 +111,42 @@ If you encounter an error like this MacOS while running `yarn start`:
     [ERROR] dshop.queues.etlProcessor: Job failed: DatabaseError [SequelizeDatabaseError]: relation "shop_domains" does not exist
 
 `cd` into /backend and run `npm run migrate`
+
+
+### Troubleshooting issues with Macs based on the Apple M1 chip 
+
+Support for new macs that use the arm64 CPU architecture is growing, but limited. Until more support is available for the hardware, one might consider it best to [run the Terminal app using Rosetta 2]. For those that prefer to use the Terminal's default settings:
+
+#### Puppeteer package incompatability
+If you encounter [this error](https://github.com/puppeteer/puppeteer/issues/6622) while running `yarn install`:
+
+    error path-to-project/node_modules/puppeteer: Command failed.
+    Exit code: 1
+    Command: node install.js
+    Arguments:
+    Directory: path-to-project/node_modules/puppeteer
+    Output:
+    The chromium binary is not available for arm64:
+    If you are on Ubuntu, you can install with:
+
+     apt-get install chromium-browser
+
+    path-to-project/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js:112
+                throw new Error();
+                ^
+
+- Install Chromium using the package [chrome-mac.zip](https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/818858/)
+  - After downloading and unzipping the contents of the file into the Applications folder, open it. MacOS’ security settings blocks the file execution, but one can override it by navigating to System Preferences > Security & Privacy > General, and clicking ‘Open Anyway’.
+
+- Add the following lines to ~/.zshrc:
+    ```
+    export PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
+    export PUPPETEER_EXECUTABLE_PATH=”/Applications/Chromium.app/Contents/MacOS/Chromium”
+    ```
+#### Problem with NodeJS version 14.x
+
+If you see an error along the lines of
+    
+    FATAL ERROR: wasm code commit Allocation failed - process out of memory
+
+when running `yarn start`, upgrade NodeJS to [version 15.3.0](https://nodejs.org/en/blog/release/v15.3.0/) or higher.

shop/translation/crowdin/all-messages.json

@@ -405,6 +405,7 @@
   "g6b1nxkcp50wFqi8huMmLg==": "Shipping Address",
   "Iwcp/mMEnXlgXoQvZNEK6A==": "Billing Address",
   "DJWHgiUQ4e6kW/BI8ug7lQ==": "Same as shipping address",
+  "idylnk+3UpzCtGTZ8jtqkg==": "NFT Wallet",
   "k1/F72PdYZuLJdwWqJrBcQ==": "Payment state updated!",
   "E2ZrB6RgRZtbSk5TETwODQ==": "Failed to update payment state. Try again later.",
   "cEEmDS+WPcCQO0UUnHE/gg==": "Marking",
@@ -834,6 +835,7 @@
   "FADaLalu+D372ggqeLfkoA==": "Loading shipping costs...",
   "Lv98eLSN37OEDe8w81hDTg==": "Sorry, there was an error calculating shipping costs. Try refreshing the page.",
   "tS1cMRohUZyXrVqWtdfEdg==": "Free",
+  "cxQ0rGBHF+gSLGLgvoYhLQ==": "NFT delivery",
   "yDuVfSNrX9cqD0XvSLJZEw==": "Return to information",
   "P/Dyyx60t0zWVvOdAH81ag==": "Continue to payment",
   "n64585ZhAYvhJ/feaYPwDA==": "Prices are shown in {VAR_CURRENCY_B64_Y3VycmVuY3k} for reference at the exchange rate of 1 {VAR_ACTUALCURRENCY_B64_YWN0dWFsQ3VycmVuY3k} = {VAR_EXCHANGERATE_B64_ZXhjaGFuZ2VSYXRl} {VAR_CURRENCY2_B64_Y3VycmVuY3ky}. You'll be charged in {VAR_ACTUALCURRENCY2_B64_YWN0dWFsQ3VycmVuY3ky}.",