Missing LICENSE file in npm package #1036

Activity

1. olaservo commented on Feb 4, 2026

   

   olaservo

   on Feb 4, 2026

   Member

   More actions

   @claude could you resolve this issue?

   👀React with 👀1Reacted by claude
2. olaservo

   added

   bugSomething isn't workingSomething isn't working

   on Feb 4, 2026
3. claude commented on Feb 4, 2026

   

   claudeBot

   on Feb 4, 2026 – with Claude

   Last edited by claude

   Contributor

   More actions

   Claude finished @olaservo's task in 1m 14s —— View job • claude/issue-1036-20260204-1236 • Create PR ➔

   ---

   Working on: Missing LICENSE file in npm package

   Tasks

   • Gather context and understand the issue
   • Fix the issue to include LICENSE in published packages
   • Commit and push changes
   • Provide PR creation link

   Summary

   I've successfully resolved the issue by:

   1. Copied LICENSE file to each workspace directory (cli/, client/, server/)
   2. Updated package.json in each workspace to include "LICENSE" in the files array

   This ensures that when the packages are published to npm, the LICENSE file will be included in the tarballs. I verified this using npm pack --dry-run which confirmed the LICENSE file (12.2kB) is now included in all three packages.

   Changes Made

   • cli/LICENSE, client/LICENSE, server/LICENSE: Added LICENSE file to each workspace
   • cli/package.json, client/package.json, server/package.json: Added "LICENSE" to the files array

   ---

   |
4. claude

   added a commit that references this issue on Feb 4, 2026

   fix: include LICENSE file in published npm packages

   ...

   This issue will close once commit 919590e is merged into the 'main' branch.

   919590e
5. cliffhall

   closed this as completedin #1055on Feb 14, 2026
6. pull

   added a commit that references this issue on Sep 23, 2026

   chore: add the project LICENSE and point every manifest at it (modelc…

   ...

   c0c2a20