v2.x CI broken: TS1192 on @prefresh/vite and @tailwindcss/postcss since Deno v2.8.3 (TS 6.0)
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
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from freshframework/fresh
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
freshframework/fresh#3920 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
freshframework/fresh#3833 ·
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
freshframework/fresh#3803 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
freshframework/fresh#3918 · 1 comment · 4 reactions ·
-
Tab title doesn't update to <Head> <title> when navigating to a page with another <title>Possibly taken @1AbdullahButt claimed this 7 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 57/100
freshframework/fresh#3916 ·
All issues in freshframework/fresh
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tintinweb/pi-subagents#459 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
danielmiessler/LifeOS#2830 ·
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day