Skip to content

Website: ship source maps for the playground #5077

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
bradzacher opened this issue May 25, 2022 · 0 comments · Fixed by #5129
Closed

Website: ship source maps for the playground #5077

bradzacher opened this issue May 25, 2022 · 0 comments · Fixed by #5129
Labels
accepting prs Go ahead, send a pull request that resolves this issue package: website Issues related to the @typescript-eslint website repo maintenance things to do with maintenance of the repo, and not with code/docs

Comments

@bradzacher
Copy link
Member

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.
@bradzacher bradzacher added repo maintenance things to do with maintenance of the repo, and not with code/docs accepting prs Go ahead, send a pull request that resolves this issue package: website Issues related to the @typescript-eslint website labels May 25, 2022
@armano2 armano2 moved this to Todo in Website Playground May 25, 2022
armano2 added a commit that referenced this issue May 31, 2022
@armano2
chore(website): ship source maps for playground #5077
679785a
@armano2 armano2 mentioned this issue May 31, 2022
Merged
3 tasks
@armano2 armano2 moved this from Todo to In Review in Website Playground May 31, 2022
Repository owner moved this from In Review to Done in Website Playground Jun 1, 2022
bradzacher pushed a commit that referenced this issue Jun 1, 2022
@armano2
chore(website): ship source maps for playground (#5129)
79e6419 
chore(website): ship source maps for playground #5077
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
accepting prs Go ahead, send a pull request that resolves this issue package: website Issues related to the @typescript-eslint website repo maintenance things to do with maintenance of the repo, and not with code/docs
Projects
No open projects
Website Playground
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(website): ship source maps for playground typescript-eslint/typescript-eslint
1 participant
@bradzacher