fix: drop commented import from flows index template - #641
Merged
Conversation
🦋 Changeset detectedLatest commit: c5b718c The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 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 |
This was referenced Aug 20, 2026
Merged
Contributor
Author
|
View your CI Pipeline Execution ↗ for commit c5b718c
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
Contributor
Author
jumski
changed the base branch from
portable-worker-snapshot-publish
to
graphite-base/641
August 21, 2026 16:30
jumski
force-pushed
the
portable-worker-flows-template
branch
from
August 21, 2026 16:32
f80f35e to
c5b718c
Compare
Contributor
🔍 Preview Deployment: Website✅ Deployment successful! 🔗 Preview URL: https://pr-641.pgflow.pages.dev 📝 Details:
_Last updated: _ |
Contributor
🚀 Production Deployment: Website✅ Successfully deployed to production! 🔗 Production URL: https://pgflow.dev 📝 Details:
Deployed at: 2026-08-21T18:37:31+02:00 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Why
pgflow installscaffoldedsupabase/flows/index.tswith a commented-outexample import:
// Example: export { MyFlow } from './my-flow.ts';The Supabase CLI resolves each function's import graph with a regex over raw
file text (
importPathPatterninapps/cli/src/shared/functions/deploy.ts) —it does not strip comments. The commented example matches the pattern, the
walker tries to read
supabase/flows/my-flow.ts, gets ENOENT, andsupabase startaborts on a fresh project:Reproduced in isolation: fresh
supabase init+ the comment in a transitivefile →
supabase startexits with the error above; deleting only that commentline → full stack boots.
What
flows/index.tstemplate: drop the commented example import, replace with ashort warning comment that itself contains no import-shaped text
index.tsmust not referencemy-flowVerification
vitest create-flows-directory.test.ts— 7/7 (new assertion caught anearlier draft of this fix that quoted the forbidden pattern in its own
warning comment)
importPathPatternover the generated file: only./greet-user.tsmatches, which existspgflow install→supabase startboots the full stack (previously failed at bind-mountresolution)