Skip to content

fix(node-web-interface): use the real published octobot-client - #3659

Open
Herklos wants to merge 1 commit into
devfrom
fix/node-web-interface-real-octobot-client-dep
Open

fix(node-web-interface): use the real published octobot-client#3659
Herklos wants to merge 1 commit into
devfrom
fix/node-web-interface-real-octobot-client-dep

Conversation

@Herklos

@Herklos Herklos commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #3658, now that octobot-client@0.8.0 and octobot-protocol@0.8.0 are actually published on npm.

Replaces the file:../../../../client/octobot_client_ts workaround (needed only because 0.8.0 wasn't on the registry yet) with a plain ^0.8.0 range, and drops the sdk:build/prebuild/pretest scripts that were building the sibling package locally — the published tarball already ships a built dist, so there's nothing left for them to do.

Verified: npm ci, npm run build, npm test (636/636) all pass against the real dependency.

🤖 Generated with Claude Code

octobot-client@0.8.0 (and octobot-protocol@0.8.0) are now genuinely
published on npm, so the file:../../../../client/octobot_client_ts
workaround from the previous PR — needed only because that version
didn't exist on the registry yet — is no longer needed.

- package.json: octobot-client back to a plain "^0.8.0" range.
- Dropped the sdk:build/prebuild/pretest scripts that built the
  sibling package locally before every build/test — the published
  tarball already ships a built dist, so there's nothing left for
  them to do.
- package-lock.json regenerated against the real registry package
  (verified `npm ci` succeeds, matching what CI runs), and the
  now-orphaned local-path importer entry removed.

Verified: npm ci, npm run build, npm test (636/636) all pass against
the real dependency.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Herklos
Herklos requested a review from GuillaumeDSM as a code owner August 25, 2026 16:42
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.

1 participant