v2.x CI broken: TS1192 on @prefresh/vite and @tailwindcss/postcss since Deno v2.8.3 (TS 6.0)

Open
#3,866 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
deno, typescript
Domain
ci-cd, tooling

Research direction

Start by reading the two imports named in plugin-tailwindcss/src/mod.ts:2 and plugin-vite/src/mod.ts:9, then inspect PR #3857 and the dependency release status described here. The issue reports that the workaround is already proposed and upstream fixes are partly released, so check current CI and release status first; done means v2.x CI passes without the temporary workaround once upstream fixes are available.

Written by the indexing model from the issue text.

Description

Symptom

Since June 11, 2026, all v2.x CI jobs fail at deno check --allow-import:

Found 2 errors.
error: Type checking failed.

Every open PR on v2.x shows the same failure.

Root Cause

Deno v2.8.3 bumped TypeScript from 5.9.2 to 6.0.3.
TS 6.0 changed export = in ESM context from warning to error.

Two dependencies have self-contradictory metadata:
.d.ts uses export = (CJS), package.json declares exports.import (ESM):

Import File Package Error
import twPostcss from plugin-tailwindcss/src/mod.ts:2 @tailwindcss/[email protected] TS1192
import prefresh from plugin-vite/src/mod.ts:9 @prefresh/[email protected] TS1192

Status

Dependency Fix Release
@tailwindcss/postcss tailwindcss#20219 to tailwindcss#20228 merged v4.3.1 (June 12)
@prefresh/vite prefresh#625 to prefresh#626 merged awaiting v2.x release

Temporary workaround

PR #3857 adds @ts-ignore TS1192 on both imports.
Once upstream releases land, this can be reverted.

Blocked PRs

~15 open PRs failing v2.x CI solely due to this pre-existing issue.
None of the per-PR changes are the cause.
All should become green after #3857 merges or upstream fixes land.

Dominant language
TypeScript
Stars
13.8k
Forks
757
Avg merge
3m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from freshframework/fresh

All issues in freshframework/fresh

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.