feat : added scientific notation support in TSS tokenizer

[tmdeveloper007]

Summary of What Has Been Done

Extended the TSS tokenizer in packages/tss/src/tokenizer.ts to recognize scientific notation (e.g., 1e5, 1.5e-2, 2E+3) as valid numeric tokens.

Previously, the number tokenizer only accepted digits and decimal points, so values like font-size: 1.5e-2 would incorrectly tokenize the e-2 portion as a separate Ident token.

Changes Made

packages/tss/src/tokenizer.ts

• Added scientific notation parsing after the main number loop: detects e or E, optionally consumes + or -, then consumes consecutive digits.

packages/tss/src/tokenizer.test.ts

• Added test: tokenizes scientific notation with positive exponent (1e5)
• Added test: tokenizes scientific notation with negative exponent (1.5e-2)
• Added test: tokenizes scientific notation with explicit positive sign (2E+3)

15 tokenizer tests pass.

Impact it Made

Enables TSS files to use scientific notation for numeric values, which is valid CSS syntax. Developers can now use compact scientific notation like opacity: 1e-3; instead of spelling out 0.001.

Closes #3195

**Note: Please assign this PR to the tmdeveloper007 account.

[coderabbitai]

Warning

Review limit reached

@tmdeveloper007, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a91b63f2-96e4-42a1-a0e7-37a5412065fa

📥 Commits

Reviewing files that changed from the base of the PR and between 48f63a1 and c8a1505.

📒 Files selected for processing (9)

• packages/core/src/history/CommandHistory.test.ts
• packages/core/src/history/CommandHistory.ts
• packages/motion/src/interpolate.ts
• packages/quick/src/widgets.ts
• packages/store/src/immutable.test.ts
• packages/store/src/immutable.ts
• packages/tss/src/tokenizer.test.ts
• packages/tss/src/tokenizer.ts
• packages/ui/src/Tabs.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}