bug: refactor npm tarballs include compiled native binaries
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bun, typescript
- Domain
- build-system, cli, release
Research direction
Start with the npm package metadata that defines the files allowlist, then reproduce the issue with bun pm pack --ignore-scripts after the listed build and native compilation commands. Done means the tarball contains the Node launcher, bundle, runtime assets, and standard metadata, while excluding dist/bin and stale build output.
Written by the indexing model from the issue text.
Description
Description
On the refactor branch, the npm package's files allowlist includes all of dist. Packing a workspace after compiling native binaries therefore includes dist/bin and any other stale build output in the npm tarball.
Reproduction
bun install --frozen-lockfile
bun run build
bun run compile:linux-x64
bun pm pack --ignore-scripts
tar -tzf aws-agentcore-*.tgz
No publishing is needed to reproduce this.
Actual Behavior
The tarball includes dist/bin/agentcore-linux-x64. In a local reproduction, adding just this binary increased the compressed package from 1.44 MB to 40.37 MB. Other files left under dist, such as source maps, logs, and old build directories, are also included.
The automated release currently packs before compilation, which avoids the binaries on a fresh runner, but the package metadata does not enforce that separation for manual packaging or a reused build directory.
Expected Behavior
Publish only the Node launcher, Node bundle, runtime assets, and standard package metadata to npm. Keep standalone native binaries as separate GitHub release assets, regardless of build/pack order.
Environment
- Branch:
refactor - Base commit:
4fe2c108 - Bun: 1.4.0
- Platform: Linux x64
- Dominant language
- TypeScript
- Stars
- 298
- Forks
- 99
- Avg merge
- 17h 19m
- Merged PRs (30d)
- 242
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws/agentcore-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
aws/agentcore-cli#2395 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
aws/agentcore-cli#2392 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws/agentcore-cli#2176 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws/agentcore-cli#2140 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aws/agentcore-cli#2076 ·
Maintainers usually reply within 1 day
All issues in aws/agentcore-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
diegosouzapw/OmniRoute#15401 ·
Maintainers usually reply within 2 days
-
Sign the pledgeOpen
Difficulty 1/5 Under an hour Newbie friendliness 95/100
input-output-hk/devx-updates#163 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
code-yeongyu/oh-my-openagent#9454 ·
Maintainers usually reply within 1 day