[🐞] Qwik bundle detection may implicitly depend on `package.json`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- deno, typescript
- Domain
- build-system
Research direction
Start with the Qwik Runtime bundle detection and resolution logic, then reproduce the problem with the linked Deno project by running deno task build. Done means a Deno project using deno.json(c) without a root package.json detects its generated Qwik assets without the bundle-not-found or package-name errors.
Written by the indexing model from the issue text.
Description
Which component is affected?
Qwik Runtime
Describe the bug
Related issue:
In a Deno project using deno.json(c) without a root package.json, the build completes successfully and Qwik assets are generated correctly (q-manifest.json, dist/build/q-*.js, etc.).
However, Qwik later reports:
Qwik core bundle not found, is Qwik actually used in this project?
The logs also repeatedly show:
could not read /package.json to determine package name
This suggests that part of the current bundle detection / resolution logic may still implicitly rely on a Node-style project layout with a root package.json.
Reproduction
https://github.com/quadratz/qwik-astro-issue-268-
Steps to reproduce
- Make sure you have Deno installed
- Clone this repository. (Notice that
package.jsonhas been replaced bydeno.jsonc) - Run
deno task build - Check the logs.
System Info
Dependencies:
@qwik.dev/astro 1.0.1
@qwik.dev/core 2.0.0-beta.32
astro 6.1.9
Binaries:
Deno: 2.7.13 - /usr/bin/deno
Additional Information
No response
- Dominant language
- TypeScript
- Stars
- 22.1k
- Forks
- 1.4k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 98
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from QwikDev/qwik
-
docs router V2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
DX enhancement V2
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
QwikDev/qwik#8480 · 2 comments ·
Maintainers usually reply within 1 day
-
[🐞] SSG (rc.0+) ignores ssr.noExternal: bundled deps are left external in the new "ssg" environmentOpen
Difficulty 4/5 3-5 days Newbie friendliness 52/100
QwikDev/qwik#9183 · 1 comment ·
Maintainers usually reply within 1 day
-
[🐞] <Pending> child reading a signal from its owner breaks when the owner re-renders (consumerBackRef[_EFFECT_BACK_REF].set is not a function)Possibly taken @intellix claimed this 3 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
[🐞] Async useComputed$ resolved in an out-of-order <Pending> re-runs on the client at the first unrelated re-renderPossibly taken @intellix claimed this 3 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
answerLoops/answerLoops#345 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
siyuan-note/siyuan#20313 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LanternOps/breeze#8254 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
gofish-graphics/gofish-graphics#1084 ·
Maintainers usually reply within 1 day