QwikDev / QwikDev/qwik

[🐞] Qwik bundle detection may implicitly depend on `package.json`

Open
#8,616 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug runtime
Dominant language
TypeScript
Stars
22.1k
Forks
1.4k
Avg merge
1d 10h
Merged PRs (30d)
52

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
  1. Make sure you have Deno installed
  2. Clone this repository. (Notice that package.json has been replaced by deno.jsonc)
  3. Run deno task build
  4. 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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
deno, typescript
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.