Skip to content

chore: session-ui prompt-input uses \\200B CSS escape that oxlint reports as an error, breaking bun run lint #47513

Closed

Description

@woodsonl

Description

packages/session-ui/src/v2/components/prompt-input/index.tsx uses empty:before:content-['\200B'] (a CSS hex escape for zero-width space) inside a JSX class attribute. oxc's parser reports this as a JS octal-escape early error, making bun run lint exit 1 on dev for everyone.

The string is consumed by CSS verbatim (no JS unescaping happens in a JSX attribute string), so the escape is correct at runtime — the two are just in conflict.

Steps to reproduce

  1. bun run lint at dev
  2. lint exits 1: "'0'-prefixed octal literals and octal escape sequences are deprecated" at prompt-input/index.tsx

Fix incoming in PR #47510 (class moved to a JS expression with the escape written for the JS parser — emitted string verified byte-identical); filing per the Issue First policy so the drive-by fix is referenceable.

Activity

  1. neriousy commented on Oct 20, 2026

    @neriousy
    Member

    Thanks for the report. In current v2 code, the zero-width-space placeholder is defined in a CSS file rather than a JSX attribute, removing the parsing conflict reported here, so I'm closing this as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions