Skip to content

Bug: playground in a weird state when using unsupported TS version #11281

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.

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

Open
4 tasks done
G-Rath opened this issue Jun 7, 2025 · 2 comments
Open
4 tasks done

Bug: playground in a weird state when using unsupported TS version #11281

G-Rath opened this issue Jun 7, 2025 · 2 comments
Labels
bug Something isn't working triage Waiting for team members to take a look

Comments

@G-Rath
Copy link
Contributor

G-Rath commented Jun 7, 2025

Before You File a Bug Report Please Confirm You Have Done The Following...

  • I have tried restarting my IDE and the issue persists.
  • I have updated to the latest version of the packages.
  • I have searched for related issues and found none that matched my issue.
  • I have read the FAQ and my problem is not listed.

Relevant Package

website

Playground Link

No response

Repro Code

-

ESLint Config

module.exports = {
  parser: "@typescript-eslint/parser",
  rules: {
    "@typescript-eslint/<rule-name>": ["error", ...<options>],
  },
};

tsconfig

{
  "compilerOptions": {
    // ...
  }
}

Expected Result

I'm able to use the playground

Actual Result

Most of the features don't actually seem to work - I can interact with elements like checkboxes and tabs, type in code which gets red squiggles and highlighting, but most of the interaction doesn't actually do anything e.g. switching from "code" to "tsconfig" to "eslintrc" doesn't change the editor content (though it does cause a "Visual Editor" button to appear which does nothing when clicked); likewise for the "errors", "estree", etc.

If I switch to the "ESTree" tab, I do get an "ESQuery filter" input which immediately gives me this warning when I type anything:

Invalid Selector
Cannot read properties of undefined (reading 'parse')

Image

I have tried this on both latest Chrome and Edge, with extensions installed like ublock origins (which isn't reporting anything being blocked, and has been disabled for the site with no luck), with no extensions, and a few other combos, all with the same result.

There doesn't seem to be any errors in the console

Image

Here's another set of screenshots after I've clicked through some stuff and typed again into the editor:

Image

Image

Additional Info

I'd like to have attached a screen recording, but don't have any software for that setup currently - I can look into that next week if needed.

Also let me know if there's any sections of template which you'd like filled out in some way - I skipped most of them as they didn't seem relevant and I couldn't find a more appropriate

Versions

Windows 11
Chrome 137.0.7151.69
Edge 137.0.3296.68

@G-Rath G-Rath added bug Something isn't working triage Waiting for team members to take a look labels Jun 7, 2025
Copy link

github-actions bot commented Jun 7, 2025

Uh oh! @G-Rath, at least one image you shared is missing helpful alt text. Check your issue body to fix the following violations:

  • Images should have meaningful alternative text (alt text) at line 58
  • Images should have meaningful alternative text (alt text) at line 64
  • Images should have meaningful alternative text (alt text) at line 69
  • Images should have meaningful alternative text (alt text) at line 71

Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image.

Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.

🤖 Beep boop! This comment was added automatically by github/accessibility-alt-text-bot.

@G-Rath
Copy link
Contributor Author

G-Rath commented Jun 7, 2025

ugh and of course having finally gotten around to opening this, I've realized the problem, though I think there's still a bug - I'm using the playground with TS v4 somehow which is no longer supported; going to https://typescript-eslint.io/play/#ts=5.8.2 fixes this.

But I still think there's something weird here as I had to go to the above link to resolve this - just removing the TS version wasn't enough, nor could I change the version of TypeScript to another; I assume it's because the version is being stored in the usual places, but at the least it might be a good idea to have a min. version check to ensure people are not out of range?

I assume this probably happened as a result of me using the playground sometime in the past when v4.3.5 was supported (causing it to be saved in my browser) and then have not used the playground until very recently.

@Josh-Cena Josh-Cena changed the title Bug: playground just generally doesn't work Bug: playground in a weird state when using unsupported TS version Jun 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Waiting for team members to take a look
Projects
None yet
Development

No branches or pull requests

1 participant
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy