(Twoslash) Compilation errors are silent and cause entire file to fail to render
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- build-system
Research direction
Reproduce the failure from src/content/blog/example.md using bun i, bun run dev, and bun run build, following the linked reproduction steps. Trace how Twoslash compilation errors are handled during rendering and building. Done means compilation errors produce a useful error message and prevent a successful build instead of leaving the page and output blank.
Written by the indexing model from the issue text.
Description
Thank you for making this package- it is super useful
However I find it really hard to use as if there is any sort of compilation error, nothing is logged out and the entire page I'm working on immediately goes blank
I would except some kind of error message to help debug the issue, as well as for this to prevent builds from successfully completing
Reproduction Steps
- Clone https://github.com/ethanniser/ec-twoslash-issue-repro.git
- Run
bun ithenbun run dev - Go to http://localhost:4321/blog/example/
- Observe twoslash working
- Uncomment commented lines in
src/content/blog/example.md - Observe whole page go blank
- Run
bun run build - Observe build succeed without error
- Look at
distand see that build output is also blank (like dev)
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 withstudiocms/expressive-code-twoslash
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
TRACKER
Difficulty 5/5 Over a week Newbie friendliness 25/100
withstudiocms/expressive-code-twoslash#124 · 1 comment · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Dependency Dashboard OpenTRACKER
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in withstudiocms/expressive-code-twoslash
Similar issues
-
comp/dashboard P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#117722 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·