deps(ui): Upgrade color v5 #102887
Merged
deps(ui): Upgrade color v5 #102887
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The package is esm and drops a few weird dependencies it had like is-arrayish and simple-swizzle
github-actions
bot
added
the
Scope: Frontend
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Comment on lines
83
to
88
| "@tanstack/react-query-devtools": "5.85.0", | ||
| "@tanstack/react-query-persist-client": "5.85.0", | ||
| "@tanstack/react-virtual": "^3.13.6", | ||
| "@types/color": "^3.0.3", | ||
| "@types/diff": "5.2.1", | ||
| "@types/gtag.js": "^0.0.12", | ||
| "@types/history": "^3.2.5", |
There was a problem hiding this comment.
Bug: color package v5 removes opaquer(), but code still calls it, leading to a TypeError.
Severity: CRITICAL | Confidence: 1.00
🔍 Detailed Analysis
The color package was upgraded to v5.0.2, which removed the opaquer() method. Existing code in static/app/utils/theme/theme.tsx and static/app/utils/theme/theme.chonk.tsx continues to call color(...).opaquer(1.0).string(). This will result in a TypeError: color(...).opaquer is not a function during application initialization, preventing the UI from loading.
💡 Suggested Fix
Replace all calls to color(...).opaquer(value) with color(...).alpha(value) to align with the color v5 API.
🤖 Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: package.json#L83-L88
Potential issue: The `color` package was upgraded to v5.0.2, which removed the
`opaquer()` method. Existing code in `static/app/utils/theme/theme.tsx` and
`static/app/utils/theme/theme.chonk.tsx` continues to call
`color(...).opaquer(1.0).string()`. This will result in a `TypeError: color(...).opaquer
is not a function` during application initialization, preventing the UI from loading.
Did we get this right? 👍 / 👎 to inform future reviews.
michellewzhang
approved these changes
Nov 6, 2025
Ahmed-Labs
pushed a commit
that referenced
this pull request
Nov 6, 2025
The package is now esm only and drops a few weird sub-dependencies it had like `is-arrayish` and `simple-swizzle`
Jesse-Box
pushed a commit
that referenced
this pull request
Nov 12, 2025
The package is now esm only and drops a few weird sub-dependencies it had like `is-arrayish` and `simple-swizzle`
andrewshie-sentry
pushed a commit
that referenced
this pull request
Nov 13, 2025
The package is now esm only and drops a few weird sub-dependencies it had like `is-arrayish` and `simple-swizzle`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The package is now esm only and drops a few weird sub-dependencies it had like
is-arrayishandsimple-swizzle