-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Website: ship source maps for the playground #5077
Copy link
Copy link
Closed
Labels
accepting prsGo ahead, send a pull request that resolves this issueGo ahead, send a pull request that resolves this issuepackage: websiteIssues related to the @typescript-eslint websiteIssues related to the @typescript-eslint websiterepo maintenancethings to do with maintenance of the repo, and not with code/docsthings to do with maintenance of the repo, and not with code/docs
Description
Metadata
Metadata
Assignees
Labels
accepting prsGo ahead, send a pull request that resolves this issueGo ahead, send a pull request that resolves this issuepackage: websiteIssues related to the @typescript-eslint websiteIssues related to the @typescript-eslint websiterepo maintenancethings to do with maintenance of the repo, and not with code/docsthings to do with maintenance of the repo, and not with code/docs
When triaging issues I very frequently use the playground to investigate lint rule behaviour.
It saves me having to pull main, open vscode, write test cases, etc - I can just open the playground and get instant feedback.
For the same reasons in some cases I also like to set breakpoints using the chrome dev tools to deeply investigate the result of certain code paths.
It's all super quick and convenient!
Unfortunately we don't ship source maps with our playground code. This means I have to jump through a few hoops to open the exact spot and find the rule. It's still easier/faster than going via my IDE locally, but we could be even easier!
We should ship source maps with our website to make it possible to open rule source (and the playground source!) in the browser dev tools for quick debugging.