Skip to content

Use scoped @flydotio/dockerfile package in JS docs - #2456

Open
kcmartin wants to merge 1 commit into
mainfrom
fix-flydotio-dockerfile-package
Open

Use scoped @flydotio/dockerfile package in JS docs#2456
kcmartin wants to merge 1 commit into
mainfrom
fix-flydotio-dockerfile-package

Conversation

@kcmartin

@kcmartin kcmartin commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Several JS pages instructed users to run bare npx dockerfile / bunx dockerfile. That resolves to the unrelated, unmaintained dockerfile package on npm and fails with "could not determine executable to run," rather than Fly's @flydotio/dockerfile generator.

This scopes every call to @flydotio/dockerfile across the affected pages (the-basics: dependencies, dockerfiles, database; prisma: postgres, sqlite; frameworks: nextjs, astro), including the two prose lines that describe how to run the generator.

Verification: Ran npx @flydotio/dockerfile@latest --help; the scoped spec resolves and runs (its bin is dockerfile), and every flag used in these docs (--dev, --legacy-peer-deps, --add-base, --add-build, --add-deploy/--add, --cmd, --mount-secret, --build, --arg-build, --env-base) is accepted.

Closes #2398

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.

Docs reference incorrect npm package to execute

1 participant