{"id":16317433,"url":"https://github.com/fum4/orders-app-qwik","last_synced_at":"2026-05-05T11:31:46.596Z","repository":{"id":81850115,"uuid":"601402065","full_name":"fum4/orders-app-qwik","owner":"fum4","description":"A simple orders app built with Qwik","archived":false,"fork":false,"pushed_at":"2023-05-17T18:29:32.000Z","size":429,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-05-13T16:53:40.819Z","etag":null,"topics":["qwik","qwikcity","typescript","vercel","vite"],"latest_commit_sha":null,"homepage":"https://orders-app-qwik.vercel.app","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/fum4.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,"zenodo":null}},"created_at":"2023-02-14T01:34:56.000Z","updated_at":"2023-05-24T21:21:07.000Z","dependencies_parsed_at":null,"dependency_job_id":"a39b7ad8-4a0a-4fe1-a9b5-d17fae7605d0","html_url":"https://github.com/fum4/orders-app-qwik","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/fum4/orders-app-qwik","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fum4%2Forders-app-qwik","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fum4%2Forders-app-qwik/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fum4%2Forders-app-qwik/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fum4%2Forders-app-qwik/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/fum4","download_url":"https://codeload.github.com/fum4/orders-app-qwik/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fum4%2Forders-app-qwik/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":271900779,"owners_count":24841114,"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","status":"online","status_checked_at":"2025-08-24T02:00:11.135Z","response_time":111,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"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":["qwik","qwikcity","typescript","vercel","vite"],"created_at":"2024-10-10T22:08:25.395Z","updated_at":"2026-05-05T11:31:46.561Z","avatar_url":"https://github.com/fum4.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, `order.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/guides/static-site-generation/).\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## 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## 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## Vercel Edge\n\nThis starter site is configured to deploy to [Vercel Edge Functions](https://vercel.com/docs/concepts/functions/edge-functions), which means it will be rendered at an edge location near to your users.\n\n## Installation\n\nThe adaptor will add a new `vite.config.ts` within the `adapters/` directory, and a new entry file will be created, such as:\n\n```\n└── adapters/\n    └── vercel-edge/\n        └── vite.config.ts\n└── src/\n    └── entry.vercel-edge.tsx\n```\n\nAdditionally, within the `package.json`, the `build.server` script will be updated with the Vercel Edge build.\n\n## Production build\n\nTo build the application for production, use the `build` command, this command will automatically run `pnpm build.server` and `pnpm build.client`:\n\n```shell\npnpm build\n```\n\n[Read the full guide here](https://github.com/BuilderIO/qwik/blob/main/starters/adapters/vercel-edge/README.md)\n\n## Dev deploy\n\nTo deploy the application for development:\n\n```shell\npnpm deploy\n```\n\nNotice that you might need a [Vercel account](https://docs.Vercel.com/get-started/) in order to complete this step!\n\n## Production deploy\n\nThe project is ready to be deployed to Vercel. However, you will need to create a git repository and push the code to it.\n\nYou can [deploy your site to Vercel](https://vercel.com/docs/concepts/deployments/overview) either via a Git provider integration or through the Vercel CLI.\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","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ffum4%2Forders-app-qwik","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ffum4%2Forders-app-qwik","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ffum4%2Forders-app-qwik/lists"}