Most linters tell you what's wrong. They stop there.
PasteCheck has always shown you the error and the line. But "var is discouraged" doesn't tell a beginner what to actually do about it. "Empty catch block" doesn't tell you why it matters or what to replace it with.
That changes in v1.7.
Every error and warning message now ends with one actionable sentence. Not a docs link. Not a vague suggestion. One clear fix.
Prefer 'let' or 'const' over 'var' — use 'const' if the value never changes, 'let' if it does'eval()' executes arbitrary code — dangerous and a security risk — remove it and find a safer alternative like JSON.parse() or a lookup objectEmpty catch block — errors are silently swallowed — add at least console.error(e) so failures don't disappear silently
This covers every language PasteCheck supports — JavaScript, TypeScript, Python, HTML, and CSS. 30 messages updated across the entire linter.
Two Reddit commenters validated this independently before it was built. Both said the same thing unprompted — knowing what's wrong isn't enough, you need to know what to do next. That's what v1.7 ships.
v1.8 adds something no other paste tool has.
When errors or warnings exist, a collapsible "What to do next" panel appears below the results. Not per-error guidance — big picture debugging logic. The kind of thing an experienced developer would tell you if they were sitting next to you.
- If you have errors: fix the first one before the rest. Errors cascade. One missing bracket can cause five false positives below it.
- If you have warnings only: no errors is good — work through warnings one at a time using the fix hints above.
- If you have both: ignore the warnings for now. Fix the errors first. Warnings can wait until your code runs.
It's collapsed by default. It doesn't get in the way. It's there when you need it.
Both features were designed around the same principle — PasteCheck doesn't just find your mistakes, it helps you understand them.
Built entirely from an Android phone. Live at pastecheck.co.uk.