Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Website: ship source maps for the playground #5077

Closed
Labels
accepting prsGo ahead, send a pull request that resolves this issuepackage: websiteIssues related to the @typescript-eslint websiterepo maintenancethings to do with maintenance of the repo, and not with code/docs
@bradzacher

Description

@bradzacher

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    accepting prsGo ahead, send a pull request that resolves this issuepackage: websiteIssues related to the @typescript-eslint websiterepo maintenancethings to do with maintenance of the repo, and not with code/docs

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp