{"id":15412912,"url":"https://github.com/ascorbic/qwik-test","last_synced_at":"2025-06-30T00:32:34.020Z","repository":{"id":206184712,"uuid":"716010257","full_name":"ascorbic/qwik-test","owner":"ascorbic","description":null,"archived":false,"fork":false,"pushed_at":"2023-11-08T10:24:37.000Z","size":1833,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"main","last_synced_at":"2025-05-26T00:11:50.740Z","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/ascorbic.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-11-08T09:40:56.000Z","updated_at":"2023-11-08T09:41:11.000Z","dependencies_parsed_at":null,"dependency_job_id":"23741d3d-11c6-494d-a045-321229d129ae","html_url":"https://github.com/ascorbic/qwik-test","commit_stats":{"total_commits":7,"total_committers":1,"mean_commits":7.0,"dds":0.0,"last_synced_commit":"781200c500ed7980205af0d0aab6b89ef875fb5c"},"previous_names":["ascorbic/qwik-test"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/ascorbic/qwik-test","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ascorbic%2Fqwik-test","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ascorbic%2Fqwik-test/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ascorbic%2Fqwik-test/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ascorbic%2Fqwik-test/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/ascorbic","download_url":"https://codeload.github.com/ascorbic/qwik-test/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ascorbic%2Fqwik-test/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":262689570,"owners_count":23349133,"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-10-01T16:54:49.315Z","updated_at":"2025-06-30T00:32:33.947Z","avatar_url":"https://github.com/ascorbic.png","language":"TypeScript","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 an 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 includes: 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 `pnpm qwik add`\n```\n\n## Development\n\nDevelopment mode uses [Vite's development server](https://vitejs.dev/). The `dev` command will server-side render (SSR) the output during development.\n\n```shell\nnpm start # or `pnpm 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 preview a production build locally and should not be used as a production server.\n\n```shell\npnpm preview # or `pnpm preview`\n```\n\n## Production\n\nThe production build will generate client and server modules by running both client and server build commands. The build command will use Typescript to run a type check on the source code.\n\n```shell\npnpm build # or `pnpm 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### Addition Adapter Options\n\nNetlify-specific option fields that can be passed to the adapter options:\n\n- `excludedPath` this option accepts a `string` glob pattern that represents which path pattern should not go through the generated Edge Functions.\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","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fascorbic%2Fqwik-test","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fascorbic%2Fqwik-test","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fascorbic%2Fqwik-test/lists"}