-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(qwikVite): show build/[name].js output in preview with debug mode #7293
base: main
Are you sure you want to change the base?
feat(qwikVite): show build/[name].js output in preview with debug mode #7293
Conversation
🦋 Changeset detectedLatest commit: 9f95854 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It sounds reasonable to me 👏
Nice @maiieul
commit: |
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Thanks @gioboa! The output is not perfect but it's still quite helpful imo. Also I have some files generated in the client dist output called I think it's Rollup manually generating the names with some of our generic instructions. Perhaps it would be worth manually changing the names of those core files to make it more intuitive. |
e60bd6d
to
9f95854
Compare
The optimizer changed a lot between these versions |
Since chunks are merged, the name only indicates one thing it does. Why not look at the q-manifest with a server$ call and list the origins? |
What is it?
Description
To be able to debug production-only bugs more easily, instead of checking each
q-[hash]
manually to figure out what code it refers to.Checklist
pnpm change