chore: align all package names to @trycompai scope#2309
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
PR SummaryMedium Risk Overview Updates tooling/docs and build plumbing to match the new scope. This includes Turbo/typecheck command filters, Syncpack rules, Next.js Written by Cursor Bugbot for commit 787017e. This will update automatically on new commits. Configure here. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4728169d1d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| // Resolve subpath imports like @trycompai/integration-platform/types | ||
| build.onResolve( | ||
| { filter: /^@comp\/integration-platform\// }, |
There was a problem hiding this comment.
After renaming the package to @trycompai/integration-platform, the esbuild resolver plugin in IntegrationPlatformExtension still uses @comp regex filters, so Trigger.dev builds won't intercept the new import path. In environments where the workspace package is not directly available in node_modules (the case this extension is meant to handle), imports like @trycompai/integration-platform (and subpaths) will fail to resolve during bundling.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in 955ff57 — both onResolve regex filters updated to @trycompai/integration-platform.
|
Worth testing |
- Resolve 6 merge conflicts from main (take new code with @trycompai scope) - Fix esbuild onResolve regex filters in integrationPlatformExtension.ts that still matched @comp/integration-platform instead of @trycompai/ - Fix remaining @comp/auth references in test files from main Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 955ff574cd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -1,5 +1,5 @@ | |||
| { | |||
| "name": "@comp/api", | |||
| "name": "@trycompai/api", | |||
There was a problem hiding this comment.
These package-name changes were committed without regenerating bun.lock (it still records workspaces as @comp/*), so installs that require a frozen lockfile can no longer accept the manifest state from this commit. I checked .github/workflows/release.yml (the Install dependencies step runs bun install --frozen-lockfile --ignore-scripts with no non-frozen fallback), so release/CI jobs can fail until the lockfile is updated to the new @trycompai/* workspace names.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in 6a9a5b8 — bun.lock regenerated with the new @trycompai/* workspace names.
- Fix last @comp/ui reference in CLAUDE.md design system section - Regenerate bun.lock to reflect @trycompai/* workspace names (CI with --frozen-lockfile would fail without this) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Good call — added to the test plan. Vercel preview builds for both app and portal already passed, which covers the build path. |
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| # - 'apps/api/package.json' | ||
| # - '.github/workflows/maced-contract-canary.yml' | ||
| # schedule: | ||
| # - cron: '0 * * * *' |
There was a problem hiding this comment.
CI canary workflow disabled unrelated to package rename
Low Severity
The maced-contract-canary.yml workflow's pull_request and schedule triggers are commented out, disabling both PR-triggered and hourly scheduled canary checks. This is unrelated to the package scope rename described in the PR — the PR description explicitly states "no logic changes" and only lists package renames. Bundling a CI coverage reduction into a 552-file rename PR risks it being overlooked during review. If intentional, it belongs in a separate PR with its own tracking for re-enablement.
| "packages": ["@comp/**"], | ||
| "dependencies": ["@comp/**"], | ||
| "packages": ["@trycompai/**"], | ||
| "dependencies": ["@trycompai/**"], |
There was a problem hiding this comment.
Syncpack rule now incorrectly covers external npm packages
Medium Severity
The semverGroups rule changed from @comp/** to @trycompai/** for both packages and dependencies, requiring matching deps use workspace:*. However, @trycompai/design-system is an external npm package (not a workspace package) pinned at semver ranges like ^1.0.32 in apps/app/package.json and ^1.0.43 in apps/portal/package.json. The old @comp/** pattern never matched it, but @trycompai/** does. Running syncpack lint will now incorrectly flag these as violations, and syncpack fix could corrupt them to workspace:*, which would fail resolution.
|
🎉 This PR is included in version 3.7.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
2 participants
Summary
The monorepo had an inconsistent mix of package scopes — some packages used
@comp/*while others already used@trycompai/*(the scope published to npm, e.g.@trycompai/ui). This madebun run devoutput confusing and created unnecessary cognitive overhead.This PR aligns all packages to the
@trycompai/*scope to match what's published to npm.Before → After
Already
@trycompai/(unchanged):@trycompai/analytics,@trycompai/db,@trycompai/email,@trycompai/integrations,@trycompai/kv,@trycompai/tsconfig,@trycompai/ui,@trycompai/utilsRenamed in this PR:
@comp/api@trycompai/api@comp/app@trycompai/app@comp/portal@trycompai/portal@comp/auth@trycompai/auth@comp/cli@trycompai/cli@comp/company@trycompai/company@comp/device-agent@trycompai/device-agent@comp/integration-platform@trycompai/integration-platformdocs@trycompai/docsAll import statements, dependency references, tsconfig path aliases, and config files (
turbo.json,.syncpackrc.json,buildspec.yml) updated accordingly. 552 files changed, 1296 equal insertions/deletions (clean find-and-replace, no logic changes).Test plan
bun installresolves all workspace dependenciesbun run buildsucceedsbun run typecheckpassesbun run devshows aligned@trycompai/*names🤖 Generated with Claude Code