Skip to content

fix: fall back to a Node scan when grep is unavailable#292

Open
dustinlacewell wants to merge 1 commit into
QwikDev:build/v2from
dustinlacewell:grep-fallback
Open

fix: fall back to a Node scan when grep is unavailable#292
dustinlacewell wants to merge 1 commit into
QwikDev:build/v2from
dustinlacewell:grep-fallback

Conversation

@dustinlacewell

Copy link
Copy Markdown

When trying to upgrade my site to Qwik2 / Astro 6, every page dies with Q14 -- but only on Windows. It seems scanQwikEntrypoints in scan.ts shells out to grep with config.root.pathname as cwd which ends up being something like /C:/foo/bar/ so the spawn throws ENOENT and then the bare catch there eats it. The integration thinks there are no entrypoints, skips the standalone client build, no q-manifest.json exists and prerender time, Q14 on every QRL.

I got it fixed with a patch to use a pure-nodejs walk instead of the grep shell + fileURLToPath just to see if that was it, and it seemed to work.

This PR fixes the path format but also fallback to this node walk if grep is not available.

@changeset-bot

changeset-bot Bot commented Jul 11, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: e69b73f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@qwik.dev/astro Patch
netlify-fixture Patch
node-fixture Patch
vercel-fixture Patch

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

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.

1 participant