{"id":18556011,"url":"https://github.com/codigoencasa/chatbot-play","last_synced_at":"2025-06-26T01:35:16.487Z","repository":{"id":105789930,"uuid":"597869538","full_name":"codigoencasa/chatbot-play","owner":"codigoencasa","description":"Runkit (Playground)","archived":false,"fork":false,"pushed_at":"2023-02-27T22:01:09.000Z","size":4379,"stargazers_count":0,"open_issues_count":0,"forks_count":1,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-02-17T11:32:27.292Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/codigoencasa.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-02-05T21:38:49.000Z","updated_at":"2023-02-24T12:18:16.000Z","dependencies_parsed_at":"2023-03-06T14:30:24.879Z","dependency_job_id":null,"html_url":"https://github.com/codigoencasa/chatbot-play","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/codigoencasa%2Fchatbot-play","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/codigoencasa%2Fchatbot-play/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/codigoencasa%2Fchatbot-play/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/codigoencasa%2Fchatbot-play/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/codigoencasa","download_url":"https://codeload.github.com/codigoencasa/chatbot-play/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254346626,"owners_count":22055809,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-06T21:28:44.200Z","updated_at":"2025-05-15T13:10:45.017Z","avatar_url":"https://github.com/codigoencasa.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Qwik City App ⚡️\n\n- [Qwik Docs](https://qwik.builder.io/)\n- [Discord](https://qwik.builder.io/chat)\n- [Qwik GitHub](https://github.com/BuilderIO/qwik)\n- [@QwikDev](https://twitter.com/QwikDev)\n- [Vite](https://vitejs.dev/)\n\n---\n\n## Project Structure\n\nThis project is using Qwik with [QwikCity](https://qwik.builder.io/qwikcity/overview/). QwikCity is just a extra set of tools on top of Qwik to make it easier to build a full site, including directory-based routing, layouts, and more.\n\nInside your project, you'll see the following directory structure:\n\n```\n├── public/\n│   └── ...\n└── src/\n    ├── components/\n    │   └── ...\n    └── routes/\n        └── ...\n```\n\n- `src/routes`: Provides the directory based routing, which can include a hierarchy of `layout.tsx` layout files, and an `index.tsx` file as the page. Additionally, `index.ts` files are endpoints. Please see the [routing docs](https://qwik.builder.io/qwikcity/routing/overview/) for more info.\n\n- `src/components`: Recommended directory for components.\n\n- `public`: Any static assets, like images, can be placed in the public directory. Please see the [Vite public directory](https://vitejs.dev/guide/assets.html#the-public-directory) for more info.\n\n## Add Integrations and deployment\n\nUse the `pnpm qwik add` command to add additional integrations. Some examples of integrations include: Cloudflare, Netlify or Express server, and the [Static Site Generator (SSG)](https://qwik.builder.io/qwikcity/static-site-generation/static-site-config/).\n\n```shell\npnpm qwik add # or `yarn qwik add`\n```\n\n## Development\n\nDevelopment mode uses [Vite's development server](https://vitejs.dev/). During development, the `dev` command will server-side render (SSR) the output.\n\n```shell\nnpm start # or `yarn start`\n```\n\n\u003e Note: during dev mode, Vite may request a significant number of `.js` files. This does not represent a Qwik production build.\n\n## Preview\n\nThe preview command will create a production build of the client modules, a production build of `src/entry.preview.tsx`, and run a local server. The preview server is only for convenience to locally preview a production build, and it should not be used as a production server.\n\n```shell\npnpm preview # or `yarn preview`\n```\n\n## Production\n\nThe production build will generate client and server modules by running both client and server build commands. Additionally, the build command will use Typescript to run a type check on the source code.\n\n```shell\npnpm build # or `yarn build`\n```\n\n## Express Server\n\nThis app has a minimal [Express server](https://expressjs.com/) implementation. After running a full build, you can preview the build using the command:\n\n```\npnpm serve\n```\n\nThen visit [http://localhost:8080/](http://localhost:8080/)\n\n## Netlify\n\nThis starter site is configured to deploy to [Netlify Edge Functions](https://docs.netlify.com/edge-functions/overview/), which means it will be rendered at an edge location near to your users.\n\n### Local development\n\nThe [Netlify CLI](https://docs.netlify.com/cli/get-started/) can be used to preview a production build locally. To do so: First build your site, then to start a local server, run:\n\n1. Install Netlify CLI globally `npm i -g netlify-cli`.\n2. Build your site with both ssr and static `pnpm build`.\n3. Start a local server with `pnpm serve`.\n   In this project, `pnpm serve` uses the `netlify dev` command to spin up a server that can handle Netlify's Edge Functions locally.\n4. Visit [http://localhost:8888/](http://localhost:8888/) to check out your site.\n\n### Edge Functions Declarations\n\n[Netlify Edge Functions declarations](https://docs.netlify.com/edge-functions/declarations/)\ncan be configured to run on specific URL patterns. Each edge function declaration associates\none site path pattern with one function to execute on requests that match the path. A single request can execute a chain of edge functions from a series of declarations. A single edge function can be associated with multiple paths across various declarations.\n\nThis is useful to determine if a page response should be Server-Side Rendered (SSR) or\nif the response should use a static-site generated (SSG) `index.html` file instead.\n\nBy default, the Netlify Edge adaptor will generate a `.netlify/edge-middleware/manifest.json` file, which is used by the Netlify deployment to determine which paths should, and should not, use edge functions.\n\nTo override the generated manifest, you can [add a declaration](https://docs.netlify.com/edge-functions/declarations/#add-a-declaration) to the `netlify.toml` using the `[[edge_functions]]` config. For example:\n\n```toml\n[[edge_functions]]\n  path = \"/admin\"\n  function = \"auth\"\n```\n\n### Deployments\n\nYou can [deploy your site to Netlify](https://docs.netlify.com/site-deploys/create-deploys/) either via a Git provider integration or through the Netlify CLI. This starter site includes a `netlify.toml` file to configure your build for deployment.\n\n#### Deploying via Git\n\nOnce your site has been pushed to your Git provider, you can either link it [in the Netlify UI](https://app.netlify.com/start) or use the CLI. To link your site to a Git provider from the Netlify CLI, run the command:\n\n```shell\nnetlify link\n```\n\nThis sets up [continuous deployment](https://docs.netlify.com/site-deploys/create-deploys/#deploy-with-git) for your site's repo. Whenever you push new commits to your repo, Netlify starts the build process..\n\n#### Deploying manually via the CLI\n\nIf you wish to deploy from the CLI rather than using Git, you can use the command:\n\n```shell\nnetlify deploy --build\n```\n\nYou must use the `--build` flag whenever you deploy. This ensures that the Edge Functions that this starter site relies on are generated and available when you deploy your site.\n\nAdd `--prod` flag to deploy to production.\n\n## Express Server\n\nThis app has a minimal [Express server](https://expressjs.com/) implementation. After running a full build, you can preview the build using the command:\n\n```\npnpm serve\n```\n\nThen visit [http://localhost:8080/](http://localhost:8080/)\n\n## Netlify\n\nThis starter site is configured to deploy to [Netlify Edge Functions](https://docs.netlify.com/edge-functions/overview/), which means it will be rendered at an edge location near to your users.\n\n### Local development\n\nThe [Netlify CLI](https://docs.netlify.com/cli/get-started/) can be used to preview a production build locally. To do so: First build your site, then to start a local server, run:\n\n1. Install Netlify CLI globally `npm i -g netlify-cli`.\n2. Build your site with both ssr and static `pnpm build`.\n3. Start a local server with `pnpm serve`.\n   In this project, `pnpm serve` uses the `netlify dev` command to spin up a server that can handle Netlify's Edge Functions locally.\n4. Visit [http://localhost:8888/](http://localhost:8888/) to check out your site.\n\n### Edge Functions Declarations\n\n[Netlify Edge Functions declarations](https://docs.netlify.com/edge-functions/declarations/)\ncan be configured to run on specific URL patterns. Each edge function declaration associates\none site path pattern with one function to execute on requests that match the path. A single request can execute a chain of edge functions from a series of declarations. A single edge function can be associated with multiple paths across various declarations.\n\nThis is useful to determine if a page response should be Server-Side Rendered (SSR) or\nif the response should use a static-site generated (SSG) `index.html` file instead.\n\nBy default, the Netlify Edge adaptor will generate a `.netlify/edge-middleware/manifest.json` file, which is used by the Netlify deployment to determine which paths should, and should not, use edge functions.\n\nTo override the generated manifest, you can [add a declaration](https://docs.netlify.com/edge-functions/declarations/#add-a-declaration) to the `netlify.toml` using the `[[edge_functions]]` config. For example:\n\n```toml\n[[edge_functions]]\n  path = \"/admin\"\n  function = \"auth\"\n```\n\n### Deployments\n\nYou can [deploy your site to Netlify](https://docs.netlify.com/site-deploys/create-deploys/) either via a Git provider integration or through the Netlify CLI. This starter site includes a `netlify.toml` file to configure your build for deployment.\n\n#### Deploying via Git\n\nOnce your site has been pushed to your Git provider, you can either link it [in the Netlify UI](https://app.netlify.com/start) or use the CLI. To link your site to a Git provider from the Netlify CLI, run the command:\n\n```shell\nnetlify link\n```\n\nThis sets up [continuous deployment](https://docs.netlify.com/site-deploys/create-deploys/#deploy-with-git) for your site's repo. Whenever you push new commits to your repo, Netlify starts the build process..\n\n#### Deploying manually via the CLI\n\nIf you wish to deploy from the CLI rather than using Git, you can use the command:\n\n```shell\nnetlify deploy --build\n```\n\nYou must use the `--build` flag whenever you deploy. This ensures that the Edge Functions that this starter site relies on are generated and available when you deploy your site.\n\nAdd `--prod` flag to deploy to production.\n\n## Express Server\n\nThis app has a minimal [Express server](https://expressjs.com/) implementation. After running a full build, you can preview the build using the command:\n\n```\npnpm serve\n```\n\nThen visit [http://localhost:8080/](http://localhost:8080/)\n\n## Netlify\n\nThis starter site is configured to deploy to [Netlify Edge Functions](https://docs.netlify.com/edge-functions/overview/), which means it will be rendered at an edge location near to your users.\n\n### Local development\n\nThe [Netlify CLI](https://docs.netlify.com/cli/get-started/) can be used to preview a production build locally. To do so: First build your site, then to start a local server, run:\n\n1. Install Netlify CLI globally `npm i -g netlify-cli`.\n2. Build your site with both ssr and static `pnpm build`.\n3. Start a local server with `pnpm serve`.\n   In this project, `pnpm serve` uses the `netlify dev` command to spin up a server that can handle Netlify's Edge Functions locally.\n4. Visit [http://localhost:8888/](http://localhost:8888/) to check out your site.\n\n### Edge Functions Declarations\n\n[Netlify Edge Functions declarations](https://docs.netlify.com/edge-functions/declarations/)\ncan be configured to run on specific URL patterns. Each edge function declaration associates\none site path pattern with one function to execute on requests that match the path. A single request can execute a chain of edge functions from a series of declarations. A single edge function can be associated with multiple paths across various declarations.\n\nThis is useful to determine if a page response should be Server-Side Rendered (SSR) or\nif the response should use a static-site generated (SSG) `index.html` file instead.\n\nBy default, the Netlify Edge adaptor will generate a `.netlify/edge-middleware/manifest.json` file, which is used by the Netlify deployment to determine which paths should, and should not, use edge functions.\n\nTo override the generated manifest, you can [add a declaration](https://docs.netlify.com/edge-functions/declarations/#add-a-declaration) to the `netlify.toml` using the `[[edge_functions]]` config. For example:\n\n```toml\n[[edge_functions]]\n  path = \"/admin\"\n  function = \"auth\"\n```\n\n### Deployments\n\nYou can [deploy your site to Netlify](https://docs.netlify.com/site-deploys/create-deploys/) either via a Git provider integration or through the Netlify CLI. This starter site includes a `netlify.toml` file to configure your build for deployment.\n\n#### Deploying via Git\n\nOnce your site has been pushed to your Git provider, you can either link it [in the Netlify UI](https://app.netlify.com/start) or use the CLI. To link your site to a Git provider from the Netlify CLI, run the command:\n\n```shell\nnetlify link\n```\n\nThis sets up [continuous deployment](https://docs.netlify.com/site-deploys/create-deploys/#deploy-with-git) for your site's repo. Whenever you push new commits to your repo, Netlify starts the build process..\n\n#### Deploying manually via the CLI\n\nIf you wish to deploy from the CLI rather than using Git, you can use the command:\n\n```shell\nnetlify deploy --build\n```\n\nYou must use the `--build` flag whenever you deploy. This ensures that the Edge Functions that this starter site relies on are generated and available when you deploy your site.\n\nAdd `--prod` flag to deploy to production.\n\n## Cloudflare Pages\n\nCloudflare's [wrangler](https://github.com/cloudflare/wrangler) CLI can be used to preview a production build locally. To start a local server, run:\n\n```\npnpm serve\n```\n\nThen visit [http://localhost:8787/](http://localhost:8787/)\n\n### Deployments\n\n[Cloudflare Pages](https://pages.cloudflare.com/) are deployable through their [Git provider integrations](https://developers.cloudflare.com/pages/platform/git-integration/).\n\nIf you don't already have an account, then [create a Cloudflare account here](https://dash.cloudflare.com/sign-up/pages). Next go to your dashboard and follow the [Cloudflare Pages deployment guide](https://developers.cloudflare.com/pages/framework-guides/deploy-anything/).\n\nWithin the projects \"Settings\" for \"Build and deployments\", the \"Build command\" should be `pnpm build`, and the \"Build output directory\" should be set to `dist`.\n\n### Function Invocation Routes\n\nCloudflare Page's [function-invocation-routes config](https://developers.cloudflare.com/pages/platform/functions/function-invocation-routes/) can be used to include, or exclude, certain paths to be used by the worker functions. Having a `_routes.json` file gives developers more granular control over when your Function is invoked.\nThis is useful to determine if a page response should be Server-Side Rendered (SSR) or if the response should use a static-site generated (SSG) `index.html` file.\n\nBy default, the Cloudflare pages adaptor _does not_ include a `public/_routes.json` config, but rather it is auto-generated from the build by the Cloudflare adaptor. An example of an auto-generate `dist/_routes.json` would be:\n\n```\n{\n  \"include\": [\n    \"/*\"\n  ],\n  \"exclude\": [\n    \"/_headers\",\n    \"/_redirects\",\n    \"/build/*\",\n    \"/favicon.ico\",\n    \"/manifest.json\",\n    \"/service-worker.js\",\n    \"/about\"\n  ],\n  \"version\": 1\n}\n```\n\nIn the above example, it's saying _all_ pages should be SSR'd. However, the root static files such as `/favicon.ico` and any static assets in `/build/*` should be excluded from the Functions, and instead treated as a static file.\n\nIn most cases the generated `dist/_routes.json` file is ideal. However, if you need more granular control over each path, you can instead provide you're own `public/_routes.json` file. When the project provides its own `public/_routes.json` file, then the Cloudflare adaptor will not auto-generate the routes config and instead use the committed one within the `public` directory.\n\n## Netlify\n\nThis starter site is configured to deploy to [Netlify Edge Functions](https://docs.netlify.com/edge-functions/overview/), which means it will be rendered at an edge location near to your users.\n\n### Local development\n\nThe [Netlify CLI](https://docs.netlify.com/cli/get-started/) can be used to preview a production build locally. To do so: First build your site, then to start a local server, run:\n\n1. Install Netlify CLI globally `npm i -g netlify-cli`.\n2. Build your site with both ssr and static `pnpm build`.\n3. Start a local server with `pnpm serve`.\n   In this project, `pnpm serve` uses the `netlify dev` command to spin up a server that can handle Netlify's Edge Functions locally.\n4. Visit [http://localhost:8888/](http://localhost:8888/) to check out your site.\n\n### Edge Functions Declarations\n\n[Netlify Edge Functions declarations](https://docs.netlify.com/edge-functions/declarations/)\ncan be configured to run on specific URL patterns. Each edge function declaration associates\none site path pattern with one function to execute on requests that match the path. A single request can execute a chain of edge functions from a series of declarations. A single edge function can be associated with multiple paths across various declarations.\n\nThis is useful to determine if a page response should be Server-Side Rendered (SSR) or\nif the response should use a static-site generated (SSG) `index.html` file instead.\n\nBy default, the Netlify Edge adaptor will generate a `.netlify/edge-middleware/manifest.json` file, which is used by the Netlify deployment to determine which paths should, and should not, use edge functions.\n\nTo override the generated manifest, you can [add a declaration](https://docs.netlify.com/edge-functions/declarations/#add-a-declaration) to the `netlify.toml` using the `[[edge_functions]]` config. For example:\n\n```toml\n[[edge_functions]]\n  path = \"/admin\"\n  function = \"auth\"\n```\n\n### Deployments\n\nYou can [deploy your site to Netlify](https://docs.netlify.com/site-deploys/create-deploys/) either via a Git provider integration or through the Netlify CLI. This starter site includes a `netlify.toml` file to configure your build for deployment.\n\n#### Deploying via Git\n\nOnce your site has been pushed to your Git provider, you can either link it [in the Netlify UI](https://app.netlify.com/start) or use the CLI. To link your site to a Git provider from the Netlify CLI, run the command:\n\n```shell\nnetlify link\n```\n\nThis sets up [continuous deployment](https://docs.netlify.com/site-deploys/create-deploys/#deploy-with-git) for your site's repo. Whenever you push new commits to your repo, Netlify starts the build process..\n\n#### Deploying manually via the CLI\n\nIf you wish to deploy from the CLI rather than using Git, you can use the command:\n\n```shell\nnetlify deploy --build\n```\n\nYou must use the `--build` flag whenever you deploy. This ensures that the Edge Functions that this starter site relies on are generated and available when you deploy your site.\n\nAdd `--prod` flag to deploy to production.\n\n## Express Server\n\nThis app has a minimal [Express server](https://expressjs.com/) implementation. After running a full build, you can preview the build using the command:\n\n```\nnpm run serve\n```\n\nThen visit [http://localhost:8080/](http://localhost:8080/)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcodigoencasa%2Fchatbot-play","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcodigoencasa%2Fchatbot-play","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcodigoencasa%2Fchatbot-play/lists"}