docs(publishing): scaffold a package with npm create malloy-package - #332
Merged
mtoy-googly-moogly merged 2 commits intoJul 24, 2026
Merged
Conversation
The Quick Start opened by asking the reader to hand-build a package directory and a manifest. The scaffolder does that for them, registers the package so the server actually serves it, and sets up the workspace around it, so it belongs first, with the by-hand layout kept underneath for anyone who wants it. Both the `npm create` and `npx` forms are shown, because they parse options differently and getting it wrong fails in a way a reader cannot reason about: `npm create` treats anything before a `--` as one of its own options, so the separator is required, while `npx` forwards flags untouched and counts a `--` as an extra argument. Verified against both entry points rather than assumed. Both require Node, which is worth stating plainly on a page a non-developer may land on. Do not merge before `create-malloy-package` is published to npm: it is unregistered today, so this page would tell readers to run a name anyone can take. Signed-off-by: Monty Lennie <montylennie@gmail.com>
mlennie
force-pushed
the
monty/document-create-malloy-package
branch
from
July 24, 2026 15:34
b487cfe to
46ae69a
Compare
Match the same rewording applied to the Publisher README: say "your own data" rather than "a CSV or Parquet file", keep the accurate `--data` file list (CSV, Parquet, Excel), and add that a package's model can point at a database connection the config defines, so the same workspace serves a warehouse. Signed-off-by: Monty Lennie <montylennie@gmail.com>
mlennie
added a commit
to mlennie/malloydata.github.io
that referenced
this pull request
Jul 24, 2026
The scaffolder was republished as @malloy-publisher/create-malloy-package and the old unscoped create-malloy-package was unpublished, so the quick start must show `npm create @malloy-publisher/malloy-package` / `npx @malloy-publisher/create-malloy-package`. The unscoped command now 404s. Follow-up to the merged malloydata#332. Signed-off-by: Monty Lennie <montylennie@gmail.com>
mtoy-googly-moogly
pushed a commit
that referenced
this pull request
Jul 24, 2026
The scaffolder was republished as @malloy-publisher/create-malloy-package and the old unscoped create-malloy-package was unpublished, so the quick start must show `npm create @malloy-publisher/malloy-package` / `npx @malloy-publisher/create-malloy-package`. The unscoped command now 404s. Follow-up to the merged #332. Signed-off-by: Monty Lennie <montylennie@gmail.com>
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
2 participants
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.
The Quick Start opened by asking the reader to hand-build a package directory and a manifest. The scaffolder does that for them, registers the package so the server actually serves it, and sets up the workspace around it, so it belongs first, with the by-hand layout kept underneath for anyone who wants it.
Both the
npm createandnpxforms are shown, because they parse options differently and getting it wrong fails in a way a reader cannot reason about:npm createtreats anything before a--as one of its own options, so the separator is required, whilenpxforwards flags untouched and counts a--as an extra argument. Verified against both entry points rather than assumed.Both require Node, which is worth stating plainly on a page a non-developer may land on.
The framing points at "your own data" rather than a specific file type:
--dataseeds the starter model from a local CSV, Parquet, or Excel file, and a note says a package's model can also point at a database connection the config defines, so the same workspace serves a warehouse. This matches the same rewording on the Publisher README (malloydata/publisher#910).The merge-order caveat this PR originally carried is now cleared:
create-malloy-packageis published to npm (as is@malloy-publisher/skills, which it installs), and I verified the command scaffolds a real package and copies the skills end to end from the live registry.