Skip to content

Twiggeh/qwik-report

Repository files navigation

Qwik City App ⚡️


Project Structure

This project is using Qwik with QwikCity. 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.

Inside your project, you'll see the following directory structure:

├── public/
│   └── ...
└── src/
    ├── components/
    │   └── ...
    └── routes/
        └── ...
  • 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 for more info.

  • src/components: Recommended directory for components.

  • public: Any static assets, like images, can be placed in the public directory. Please see the Vite public directory for more info.

Add Integrations and deployment

Use the bun qwik add command to add additional integrations. Some examples of integrations includes: Cloudflare, Netlify or Express Server, and the Static Site Generator (SSG).

bun qwik add # or `bun qwik add`

Development

Development mode uses Vite's development server. The dev command will server-side render (SSR) the output during development.

npm start # or `bun start`

Note: during dev mode, Vite may request a significant number of .js files. This does not represent a Qwik production build.

Preview

The 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.

bun preview # or `bun preview`

Production

The 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.

bun build # or `bun build`

Bun Server

This app has a minimal Bun server implementation. After running a full build, you can preview the build using the command:

bun run serve

Then visit https://localhost:3000/

Bun Server

This app has a minimal Bun server implementation. After running a full build, you can preview the build using the command:

bun run serve

Then visit https://localhost:3000/

Bun Server

This app has a minimal Bun server implementation. After running a full build, you can preview the build using the command:

bun run serve

Then visit https://localhost:3000/

Bun Server

This app has a minimal Bun server implementation. After running a full build, you can preview the build using the command:

bun run serve

Then visit https://localhost:3000/

Bun Server

This app has a minimal Bun server implementation. After running a full build, you can preview the build using the command:

bun run serve

Then visit https://localhost:3000/

Bun Server

This app has a minimal Bun server implementation. After running a full build, you can preview the build using the command:

bun run serve

Then visit https://localhost:3000/

Bun Server

This app has a minimal Bun server implementation. After running a full build, you can preview the build using the command:

bun run serve

Then visit https://localhost:3000/

Bun Server

This app has a minimal Bun server implementation. After running a full build, you can preview the build using the command:

bun run serve

Then visit https://localhost:3000/

Bun Server

This app has a minimal Bun server implementation. After running a full build, you can preview the build using the command:

bun run serve

Then visit https://localhost:3000/

Bun Server

This app has a minimal Bun server implementation. After running a full build, you can preview the build using the command:

bun run serve

Then visit https://localhost:3000/