Files
llmx/llmx-cli/scripts
Sebastian Krüger 8c04526619 fix(build): accept scoped package name @valknarthing/llmx in build script
The build_npm_package.py script now accepts '@valknarthing/llmx' as a valid
--package argument and normalizes it to 'llmx' internally for processing.

This allows the workflow to use the full scoped package name for clarity
while maintaining backward compatibility with the 'llmx' identifier.
2025-11-13 07:42:12 +01:00
..

npm releases

Use the staging helper in the repo root to generate npm tarballs for a release. For example, to stage the CLI, responses proxy, and SDK packages for version 0.6.0:

./scripts/stage_npm_packages.py \
  --release-version 0.6.0 \
  --package llmx \
  --package llmx-responses-api-proxy \
  --package llmx-sdk

This downloads the native artifacts once, hydrates vendor/ for each package, and writes tarballs to dist/npm/.

If you need to invoke build_npm_package.py directly, run llmx-cli/scripts/install_native_deps.py first and pass --vendor-src pointing to the directory that contains the populated vendor/ tree.