Skip to content

Conversation

@gioboa
Copy link

@gioboa gioboa commented Oct 14, 2025

I added the nitro plugin on top of a minimal Qwik SSR configuration.

  • dev
  • build
  • preview

@gioboa gioboa force-pushed the feat/add-qwik branch 7 times, most recently from dfa0fcf to d823c90 Compare October 14, 2025 15:41
@gioboa gioboa marked this pull request as ready for review October 14, 2025 20:15
@gioboa gioboa force-pushed the feat/add-qwik branch 2 times, most recently from 206aa11 to eddd119 Compare October 14, 2025 20:16
"build.preview": "vite build --ssr src/entry.preview.tsx",
"build.types": "tsc --incremental --noEmit",
"dev": "vite --open --mode ssr",
"preview": "qwik build preview && cp -r ./dist/* ./.output/public/ && vite preview --open",
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This cp step is needed b/c some files are missing in the .output folder. 🤔

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should remove this extra step to have the possibility to use nitro presets 👀

@gioboa
Copy link
Author

gioboa commented Oct 14, 2025

Screenshot 2025-10-14 at 22 19 32

@pi0 pi0 changed the title feat: add Qwik example feat: add qwik example Oct 15, 2025
@pi0
Copy link
Member

pi0 commented Oct 15, 2025

Thanks for the PR! I have done a quick local test. Qwik vite plugin works perfectly well on it's own but adding server entry or server routes breaks both dev and prod.

The requirement is, we need the Quik plugin to configure ssr environment with a rollup entry that points to a file exporting { fetch: Request => Response } so that nitro can wire it up both for local and also agnostic server.

Please LMK if wanted to chat about this.

@pi0 pi0 marked this pull request as draft October 15, 2025 07:37
untested because nitro fails to fallback to our server

Co-authored-by: Giorgio Boa <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants