cloudcommerce 0.36.2 → 0.37.1

package/ecomplus-stores/monocard/.vscode/settings.json

@@ -1,13 +0,0 @@
-{
-  "editor.quickSuggestions": {
-    "strings": true
-  },
-  "editor.codeActionsOnSave": {
-    "source.fixAll.eslint": true
-  },
-  "files.associations": {
-    "*.css": "tailwindcss"
-  },
-  "css.lint.unknownAtRules": "ignore",
-  "git.autofetch": true
-}

package/ecomplus-stores/monocard/LICENSE.md

@@ -1,230 +0,0 @@
-“Commons Clause” License Condition v1.0
-
-The Software is provided to you by the Licensor under the
-License, as defined below, subject to the following condition.
-
-Without limiting other conditions in the License, the grant
-of rights under the License will not include, and the License
-does not grant to you, the right to Sell the Software.
-
-For purposes of the foregoing, “Sell” means practicing any or
-all of the rights granted to you under the License to provide
-to third parties, for a fee or other consideration (including
-without limitation fees for hosting or consulting/ support
-services related to the Software), a product or service whose
-value derives, entirely or substantially, from the functionality
-of the Software. Any license notice or attribution required by
-the License must also include this Commons Clause License
-Condition notice.
-
-Software: E-Com Plus Open Cloud Commerce
-
-License: Apache 2.0 with Commons Clause
-
-Licensor: E-Com Club Softwares para E-commerce
-
-
----------------------------------------------------------------------
-
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright 2021 E-Com Club Softwares para E-commerce
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

package/ecomplus-stores/monocard/README.md

@@ -1,31 +0,0 @@
-# Store
-
-[Cloud Commerce](https://github.com/ecomplus/cloud-commerce): the new Store template
-
-## Getting started
-
-[:us: First deployment and setup](./SETUP.md)
-
-[:brazil: Primeiro deploy e configuração](./SETUP.pt-BR.md)
-
-## Local development
-
-```bash
-npm i
-```
-
-> **Note**  
-> Check VS Code (highly) recommend extensions in _store/.vscode/extensions.json_
-
-### Storefront
-
-```bash
-npm run dev
-```
-
-It starts serving the site at http://localhost:3000/.
-
-Edit your store source in _functions/ssr_:
-- _src_: pages, components, styles and scripts sources;
-- _content_: JSON and Markdown content (editable with git-based CMS);
-- _public_: images and not-parsed static assets;

package/ecomplus-stores/monocard/SETUP.md

@@ -1,129 +0,0 @@
-# Store
-
-[Cloud Commerce](https://github.com/ecomplus/cloud-commerce): the new Store template
-
-[:brazil: Tradução em português](./SETUP.pt-BR.md)
-
-## Getting started
-
-1. Start creating new project on [Firebase console](https://console.firebase.google.com/):
-    - Set a nice project name (ID) and remember it;
-    - Disable (recommended) Google Analytics for Firebase, will not be used by default;
-
-2. Go to _Creation > Firestore Database_ page (on sidebar) and _Create database_:
-    - Just bypass with default production mode and rules;
-    - Select region `us-east4` (recommended, or multi-region `nam5 (us-central)`);
-
-3. Go to _Creation > Authentication_ and click _Get started_:
-    - Click _Native providers > Email/password_ and enable _Email link (login without password)_;
-    - Optionally, add other provides by _Smartphone_ (SMS, generates additional costs) and/or social media;
-
-4. Go to :gear: _> Project configurations_ e edit:
-    - _Default location for GCP resources_: Same Firestore region (`us-east4`);
-    - _Public settings > Publicly displayed name_: Your store name;
-    - _Public settings > Support email_ (optional);
-    - Under _Your apps_ create a new Web app:
-        + Re-enter the store name and enable Firebase Hosting for the new app;
-        + Copy only the value of the `firebaseConfig` object and replace at `functions/ssr/src/scripts/InlineScripts.astro`;
-        + Just click to continue in the next steps until confirmation and return to the console;
-
-5. Firebase free plan doesn't support sending external HTTP requests, so you'll need to upgrade to _Blaze_ (on demand) plan;
-
-6. [Use this template](https://github.com/ecomplus/store/generate) to generate a new repository for your store;
-
-Proceed with:
-- [Better way using command line](#first-deploy-on-cli)
-- [Only in browser](#browser-only-setup) (may be easier but less safe, not recommended)
-
-#### First deploy on CLI
-
-7. Setup and first deploy from your terminal with [Firebase CLI](https://firebase.google.com/docs/cli):
-```bash
-# Install `firebase-tools` and login
-npm install -g firebase-tools && firebase login
-```
-```bash
-# Clone your new store repository
-git clone git@github.com:{gh-user}/{new-store}.git
-cd {new-store}
-npm i
-```
-
-<details open>
-<summary>With <a href="https://cloud.google.com/sdk/docs/install">gcloud CLI</a> (optional) installed</summary>
-
-```bash
-# Run project configuration and deploy on GitHub Actions
-FIREBASE_PROJECT_ID={project-id} npm run setup
-```
-
-> **Note**  
-> Account key created automatically with only required permissions using gcloud CLI (skip steps 6 and 7).
-
-</details>
-
-<details>
-<summary>Without gcloud CLI</summary>
-
-```bash
-# Run project configuration and first deploy
-FIREBASE_PROJECT_ID={project-id} npm run setup -- --no-gcloud
-npm run deploy
-```
-
-7. [Create a service account](https://console.cloud.google.com/iam-admin/serviceaccounts) for your Firebase project directly on Google Cloud Platform:
-    - Name it _Cloud Commerce GH Actions (YOUR REPOSITORY)_;
-    - Describe it _A service account with permission to deploy Cloud Commerce from the GitHub repository to Firebase_;
-    - Continue and select the following roles to the service account:
-        1. _Firebase Admin_
-        2. _API Keys Viewer_
-        3. _Cloud Run Viewer_
-        4. _Cloud Functions Admin_
-        5. _Artifact Registry Admin_
-        6. _App Engine Creator_
-        7. _App Engine Admin_
-        8. _Cloud Scheduler Admin_
-        8. _Service Account User_
-
-8. Back in the service accounts list, click the 3 dots (actions) and select _Manage keys_, generate and download a JSON key for the created account;
-
-</details>
-
-9. Set the following secrets to your GitHub repository (_Settings > Secrets > Actions_):
-    - `FIREBASE_SERVICE_ACCOUNT`: Paste the generated Google Cloud key JSON
-    - `ECOM_AUTHENTICATION_ID`: Get from CLI setup output
-    - `ECOM_API_KEY`: Get from CLI setup output
-
-:checkered_flag: :checkered_flag: :checkered_flag: **All done, congrats!**
-
----
-
-#### Browser-only setup
-
-> **Warning**  
-> This configuration option is less secure, we recommend [first deploy on CLI](#first-deploy-on-cli) instead.
-
-7. [Create a service account](https://console.cloud.google.com/iam-admin/serviceaccounts) for your Firebase project directly on Google Cloud Platform:
-    - Name it _Cloud Commerce GH Actions (YOUR REPOSITORY)_;
-    - Describe it _A service account with ALL permissions to deploy Cloud Commerce from the GitHub to Firebase_;
-    - Continue and select the role _Quick access > Basic > Proprietary_;
-
-8. Back in the service accounts list, click the 3 dots (actions) and select _Manage keys_, generate and download a JSON key for the created account;
-
-9. Set the following secrets to your GitHub repository (_Settings > Secrets > Actions_):
-    - `FIREBASE_SERVICE_ACCOUNT`: Paste the generated Google Cloud key JSON
-    - `ECOM_STORE_ID`: Copy your _Store ID_ on the [E-Com Plus admin](https://ecomplus.app/)
-    - `ECOM_AUTHENTICATION_ID`: Copy your _Authentication ID_ on the [E-Com Plus admin](https://ecomplus.app/)
-    - `ECOM_API_KEY`: Copy your _API Key_ on the [E-Com Plus admin](https://ecomplus.app/)
-
-## Production best practices
-
-Firebase Hosting CDN is fast, but [doesn't support cache _Stale-While-Revalidate_](https://firebase.google.com/docs/hosting/manage-cache) ([context and feature request](https://firebase.uservoice.com/forums/948424-general/suggestions/47179505-hosting-cdn-cache-stale-while-revalidate)) and Hosting proxy + Cloud Functions (even without cold starts) will never take less than 1s (TTFB will probably take ~2s). We like "instant" responses but want to keep dynamic server rendered views (for less client-side JS), so stale caching is a must and so we need another CDN layer on production.
-
-[Cloudflare](https://www.cloudflare.com/) Worker is recommended on top of Firebase Hosting + Functions for production stores (when pointing the custom domain) with the following configuration:
-
-- SSL full;
-- Page rule for \*/\* (any route) with _Cache Level: Cache Everything_;
-- [_Cache Reserve_](https://www.cloudflare.com/products/cache-reserve/) with Tiered Cache;
-- DNS **proxied** A entry pointing to your Firebase Hosting IP;
-- Worker _swr_ script with source (_quick edit_) copied from [`cloud-commerce/packages/ssr/cloudflare/swr-worker.js`](https://raw.githubusercontent.com/ecomplus/cloud-commerce/main/packages/ssr/cloudflare/swr-worker.js).

package/ecomplus-stores/monocard/SETUP.pt-BR.md

@@ -1,129 +0,0 @@
-# Store
-
-[Cloud Commerce](https://github.com/ecomplus/cloud-commerce): template para nova loja
-
-[:us: English version](./SETUP.md)
-
-## Começando
-
-1. Comece criando um novo projeto no [Firebase console](https://console.firebase.google.com/):
-    - Insira um bom nome (ID) para o projeto e lembre-se dele;
-    - Desative (recomendado) Google Analytics for Firebase, não será utilizado por padrão;
-
-2. Com o projeto criado, vá para _Criação > Firestore Database_ (menu lateral) e clique em _Criar banco de dados_:
-    - Pule com o modo e as regras de produção padrão;
-    - Selecione a região `us-east4` ([recomendado](https://github.com/ecomplus/cloud-commerce/issues/164));
-
-3. Vá para _Criação > Authentication_ e clique em _Vamos começar_:
-    - Clique em _Provedores nativos > E-mail/senha_ e ative _Link do e-mail (login sem senha)_;
-    - Opcionalmente, adicione outros fornecedores por _Smartphone_ (SMS, gera custos adicionais) e/ou redes sociais;
-
-4. Vá para :gear: _> Configurações do projeto_ e edite:
-    - _Local padrão dos recursos do GCP_: mesma região do Firestore (`us-east4`);
-    - _Configurações públicas > Nome exibido ao público_: O nome da sua loja;
-    - _Configurações públicas > E-mail para suporte_ (opcional);
-    - Em _Seus aplicativos_ crie um app Web:
-        + Insira novamente o nome da loja e ativa Firebase Hosting para o novo app;
-        + Copie apenas o valor do objeto `firebaseConfig` e substitua em `functions/ssr/src/scripts/InlineScripts.astro`;
-        + Apenas clique em prosseguir nos próximos passos até confirmar e voltar para o console;
-
-5. O plano gratuito do Firebase não é compatível com o envio de solicitações HTTP externas, portanto você precisará fazer upgrade para o plano _Blaze_ (sob demanda) no canto inferior esquerdo do console do Firebase;
-
-6. [Use esse template](https://github.com/ecomplus/store/generate) para gerar um novo repositório para sua loja;
-
-Prossiga com:
-- [Melhor maneira usando a linha de comando](#primeiro-deploy-em-cli)
-- [Apenas no navegador](#setup-somente-do-navegador) (pode ser mais fácil mas menos seguro, não recomendado)
-
-#### Primeiro deploy em CLI
-
-7. Setup e primeiro deploy pelo terminal com [Firebase CLI](https://firebase.google.com/docs/cli):
-```bash
-# Install `firebase-tools` and login
-npm install -g firebase-tools && firebase login
-```
-```bash
-# Clone your new store repository
-git clone git@github.com:{gh-user}/{new-store}.git
-cd {new-store}
-npm i
-```
-
-<details open>
-<summary>Com <a href="https://cloud.google.com/sdk/docs/install">gcloud CLI</a> (opcional) instalado</summary>
-
-```bash
-# Run project configuration and deploy on GitHub Actions
-FIREBASE_PROJECT_ID={project-id} npm run setup
-```
-
-> **Note**  
-> Chave de conta criada automaticamente apenas com as permissões necessárias usando gcloud CLI (pule as etapas 6 e 7).
-
-</details>
-
-<details>
-<summary>Sem gcloud CLI</summary>
-
-```bash
-# Run project configuration and first deploy
-FIREBASE_PROJECT_ID={project-id} npm run setup -- --no-gcloud
-npm run deploy
-```
-
-7. [Crie uma conta de serviço](https://console.cloud.google.com/iam-admin/serviceaccounts) para seu projeto do Firebase diretamente no Google Cloud Platform:
-    - Nomeie _Cloud Commerce GH Actions (YOUR REPOSITORY)_;
-    - Descreva como _A service account with permission to deploy Cloud Commerce from the GitHub repository to Firebase_;
-    - Continue e selecione as seguintes permissões:
-        1. _Administrador do Firebase_
-        2. _Leitor de chaves de API_
-        3. _Leitor do Cloud Run_
-        4. _Administrador do Cloud Functions_
-        5. _Administrador do Artifact Registry_
-        6. _Criador do App Engine_
-        7. _Administrador do App Engine_
-        8. _Administrador do Cloud Scheduler_
-        9. _Usuário da conta de serviço_
-
-8. De volta na lista de contas de serviço, clique nos 3 pontos (ações) and selecione _Gerenciar chaves_, crie e faça o download de uma nova chave JSON para a conta recém criada;
-
-</details>
-
-9. Configure os seguintes secrets no seu repositório do GitHub (_Settings > Secrets > Actions_):
-    - `FIREBASE_SERVICE_ACCOUNT`: Cole o JSON da chave do Google Cloud gerada
-    - `ECOM_AUTHENTICATION_ID`: Pegue no output do setup no CLI
-    - `ECOM_API_KEY`: Pegue no output do setup no CLI
-
-:checkered_flag: :checkered_flag: :checkered_flag: **Tudo pronto, boa!**
-
----
-
-#### Setup somente do navegador
-
-> **Warning**  
-> Essa opção de configuração é menos segura, recomendamos o [primeiro deploy em CLI](#primeiro-deploy-em-cli).
-
-7. [Crie uma conta de serviço](https://console.cloud.google.com/iam-admin/serviceaccounts) para seu projeto do Firebase diretamente no Google Cloud Platform:
-    - Nomeie _Cloud Commerce GH Actions (YOUR REPOSITORY)_;
-    - Descreva como _A service account with ALL permissions to deploy Cloud Commerce from the GitHub to Firebase_;
-    - Continue e selecione a permissão _Acesso rápido > Básico > Proprietário_;
-
-8. Back in the service accounts list, click the 3 dots (actions) and select _Manage keys_, generate and download a JSON key for the created account;
-
-9. Configure os seguintes secrets no seu repositório do GitHub (_Settings > Secrets > Actions_):
-    - `FIREBASE_SERVICE_ACCOUNT`: Cole o JSON da chave do Google Cloud gerada
-    - `ECOM_STORE_ID`: Copie seu _Store ID_ no [admin da E-Com Plus](https://ecomplus.app/)
-    - `ECOM_AUTHENTICATION_ID`: Copie seu _Authentication ID_ no [admin da E-Com Plus](https://ecomplus.app/)
-    - `ECOM_API_KEY`: Copie seu _API Key_ no [admin da E-Com Plus](https://ecomplus.app/)
-
-## Práticas recomendadas de produção
-
-O CDN do Firebase Hosting é rápido, mas [não suporta _Stale-While-Revalidate_](https://firebase.google.com/docs/hosting/manage-cache) ([contexto e feature request](https://firebase.uservoice.com/forums/948424-general/suggestions/47179505-hosting-cdn-cache-stale-while-revalidate)) e Hosting proxy + Cloud Functions (mesmo sem cold starts) nunca leva menos que 1s (TTFB provavelmente vai bater ~2s). Nós gostamos de respostas "instantâneas" mas queremos manter views dinâmicas renderizadas em servidor (por menos client-side JS), então stale caching é necessário e portanto precisamos de outra camada de CDN em produção.
-
-[Cloudflare](https://www.cloudflare.com/) Worker é recomendado na frente do Firebase Hosting + Functions para lojas em produção (quando apontando o domínio próprio) com as configurações abaixo:
-
-- SSL full;
-- Page rule para \*/\* (qualquer rota) com _Cache Level: Cache Everything_;
-- [_Cache Reserve_](https://www.cloudflare.com/products/cache-reserve/) com Tiered Cache;
-- Entrada A no DNS com **proxy ativo** apontando para o IP do seu projeto no Firebase Hosting;
-- Worker _swr_ com o código (_quick edit_) copiado de [`cloud-commerce/packages/ssr/cloudflare/swr-worker.js`](https://raw.githubusercontent.com/ecomplus/cloud-commerce/main/packages/ssr/cloudflare/swr-worker.js).

package/ecomplus-stores/monocard/functions/config.json

@@ -1,3 +0,0 @@
-{
-  "storeId": 51301
-}

package/ecomplus-stores/monocard/functions/example.env

@@ -1,10 +0,0 @@
-# Get the store credentials with `npm run setup` from project root
-ECOM_AUTHENTICATION_ID=
-ECOM_API_KEY=
-
-# Optional if `storeId` is defined in config.json
-# Automatically set on CLI setup
-ECOM_STORE_ID=
-
-# https://github.com/settings/tokens
-GITHUB_TOKEN=

package/ecomplus-stores/monocard/functions/many/index.js

@@ -1,14 +0,0 @@
-import '@cloudcommerce/firebase/lib/init';
-import config from '@cloudcommerce/firebase/config';
-import mergeConfig from './config.json' assert { type: 'json' };
-
-config.set({
-  ...mergeConfig,
-  hello: 'from store',
-});
-
-export * from '@cloudcommerce/firebase';
-
-export * from '@cloudcommerce/passport/firebase';
-
-export * from '@cloudcommerce/feeds/firebase';

package/ecomplus-stores/monocard/functions/many/package.json

@@ -1,22 +0,0 @@
-{
-  "name": "monocard-many",
-  "private": true,
-  "type": "module",
-  "scripts": {
-    "build": "echo '>> Run build from repository root'",
-    "serve": "firebase emulators:start --only functions",
-    "shell": "firebase functions:shell",
-    "start": "npm run shell",
-    "deploy": "firebase deploy --only functions",
-    "logs": "firebase functions:log"
-  },
-  "engines": {
-    "node": "18"
-  },
-  "main": "index.js",
-  "dependencies": {
-    "@cloudcommerce/feeds": "^0.33.4",
-    "@cloudcommerce/firebase": "^0.33.4",
-    "@cloudcommerce/passport": "^0.33.4"
-  }
-}

package/ecomplus-stores/monocard/functions/ssr/.eslintrc.cjs

@@ -1,6 +0,0 @@
-module.exports = {
-  extends: '../../node_modules/@cloudcommerce/eslint/storefront.eslintrc.cjs',
-  rules: {
-    'import/no-extraneous-dependencies': 'off',
-  },
-};

package/ecomplus-stores/monocard/functions/ssr/astro.config.mjs

@@ -1,4 +0,0 @@
-// eslint-disable-next-line import/no-extraneous-dependencies
-import astroConfig from '@cloudcommerce/storefront/astro.config.mjs';
-
-export default astroConfig;

package/ecomplus-stores/monocard/functions/ssr/content/extra-pages/terms.json

@@ -1,11 +0,0 @@
-{
-  "title": "Privacidade e termos de serviço",
-  "date": "",
-  "meta_title": "",
-  "meta_description": "",
-  "hero": {
-    "slides": []
-  },
-  "body": "",
-  "sections": []
-}

package/ecomplus-stores/monocard/functions/ssr/content/extra-pages/trocas.json

@@ -1,11 +0,0 @@
-{
-  "title": "Trocas e devoluções",
-  "date": "",
-  "meta_title": "",
-  "meta_description": "",
-  "hero": {
-    "slides": []
-  },
-  "body": "",
-  "sections": []
-}