How to map AEM component with SPA React/Angular component

MapTo function is provided by the AEM SPA Editor JS SDK (@adobe/aem-react-editable-components). The AEM component path /apps/jorvee/components/text represents the sling:resourceType of the AEM component. This path gets matched with the :type exposed by the JSON model observed earlier. MapTo takes care of parsing the JSON model response and passing the correct values as props to the SPA component.

MapTo('jorvee/components/text')(Text, TextEditConfig);

Above MapTo function will map your AEM Text component with SPA Text component. The complete line will be like this with export keyword.

export default MapTo('wknd-spa-react/components/text')(Text, TextEditConfig);

Reference

https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/spa-editor/react/map-components.html?lang=en 

Map AEM with React component

AEM as Cloud Service does not support custom runmode config

Adobe Experience Manager as Cloud Service (AEM as CS) doesn't support custom run mode configuration. The supported runmode configurations are:

• config (The default, applies to all AEM Services)
• config.author (Applies to all AEM Author service)
• config.author.dev (Applies to AEM Dev Author service)
• config.author.stage (Applies to AEM Staging Author service)
• config.author.prod (Applies to AEM Production Author service)
• config.publish (Applies to AEM Publish service)
• config.publish.dev (Applies to AEM Dev Publish service)
• config.publish.stage (Applies to AEM Staging Publish service)
• config.publish.prod (Applies to AEM Production Publish service)
• config.dev (Applies to AEM Dev services)
• config.stage (Applies to AEM Staging services)
• config.prod (Applies to AEM Production services)

fatal: unable to access 'https://jorvee.bitbucket.com/branch/src/': SSL certificate problem: unable to get local issuer certificate

Error: 

fatal: unable to access 'https://jorvee.bitbucket.com/branch/src/': SSL certificate problem: unable to get local issuer certificate

Resolution: 

There is a workaround to disable the ssl and bypass the check. Use the below command to overcome from this error. 

For only current repository

git config http.sslVerify false

For disable the ssl at global level 

git config --global http.sslVerify false

Now you can run your git commands without any trouble. Thank you!