Mateusz Burzyński

> Telling users to point to another package for JSX would work, but I'm worried that this approach breaks as soon as there is another package that also wants to...

@RyanCavanaugh all cases from the first post in [47599](https://github.com/microsoft/TypeScript/issues/47599#issue-1114250433) work OK since 4.7: [TS playground](https://www.typescriptlang.org/play?ts=4.7.4#code/CYUwxgNghgTiAEAzArgOzAFwJYHtXzCgggEkMAeAFQD4AKHAIwCsAueAbwCh4f4AHGDmDIwINrVRtUyALYMQMAJTwAvNXiUANN15g8AZ1lj4tAB5tKytfABuOLME4BfRWzsOA3J06FiZWly8-ILCouJW6gAM2kF6qIYyxvjWqAB0GDgAYlimIMC0is6KXj5EpBgBOjwCQiLGAPpQqlExugZGUs3waRnZufmFLiW+5ZVBNaEgBRxVQfBwGMgw+JFeQU6tPHEJSV09WTl5BUUeQA). Do you have any additional test cases for this PR based on that issue? Could...

I would say that yes, this might deserve a new issue - it doesn't exactly look like the one that is being fixed here.

@RyanCavanaugh it seems that this got fixed by intra-inference improvements in 4.7, all reported playgrounds work: - [@MikeYermolayev's case](https://www.typescriptlang.org/play?ts=4.7.4#code/C4TwDgpgBAwg9gOwRAxsOAnKBeKAeAKCmKgEEUUIBnKgFTgGsIECA+ACjjGCoC4oA3kRIBzCMHKUa9JgnYBLBGACuwfgJRwAJhH5VgGRSIC+ASn4AFDHAC28qhDyTqdRs1YBuYcQBuAQwAbeS0-YAhSVQALBSVVdQAzeQgArT4yChcZZjNLazsHPAEEPxtdKH1DBBNPAjMcVig-BBAvAk0EfSh25DRMfngkVHQsXBiwU3qoZQQdROQtAjbEHuH2IRIoMQkM6TcEfj8qEAQUKHYJ7Aa19Fl+AHIb5juzABpvKH8gkLCI4EiDo4nM4CRLJVJ1S6CKAAemhoJSaQEj325QMRmM7w2sI2ONxJAAegB+TEkDDiZQYBCCYqle4ARwA7hBnu8MWZFt0hpg1u8ts5drdGoDTmMLlckXt7sjnqYXjDoVBSghgPJEFBFCpgI0MCJlEqtQAjMl+BhUdUIeIQMknCDvT7BULhKIA44ikFJBEQhoCeVQeGpfjTBgIOAMlh430RqNEknEMnAClUoolMp3RnMjEbNmmRZAA) - [@jkillian's case](https://www.typescriptlang.org/play?ts=4.7.4#code/C4TwDgpgBAkgdmArsAIgQ2GqBeKBvKAZwHsBbCAOUVIC4o5qAjCAJwG4oBfAKG9EigB5MMACWxOIQA8AFQB8OfNyhEIAGwgBjYMRZ0AFABMMaOvCSoTAShwKZbZVAgBHRGjWjQAMTgB+A6ZQMgA0UIx0MjbYCozExBpocA483ABmiHDa4nBQiIQQAMrqWjossnL6xCLZhHTCYhLS8lYRSiosEMCILDlVDZIAdPka2rr6eCTkVLRQAEwADJxWybwA9KtQAOKCgih0AO66ANaEUPsAFhA5wJcdAOSniVCipGAe2lD80Km6UAAGxkwfygiUM9GI-xcbg83jgf2C3HW-x+xGBolOml0HW0ahAUGIqU+4GgfwYpGYLD+3ExkmA+CgKK4ijyhWKoxY40cwxKugMgLQUQU4wZcTo-KGZEo1C4VgRSwciI2212B2OpwuV0+twgDxBOQgAA8wKJNJ4iQIfix-vzgaC9ZDXO5PCAfFSkX8UbM0RisSVcfjCV9-mSKVSaYQ6QRPUzcCyiiNSpyVNz2XyTGYEMh0JhBVBhZ6xSYJVNpUsESooU7YQFgoxc1hsI2wnLlmsNgAhACCewZaFEalOhH7V2A-o1121uqeLzeJrNQct1pMtrgYKef0rMJdcMVIuIAGZnqc-okQGHGpG94fOMz8vGeRy8Fy2aU0znbHmo3F94XMMWpaQMrlk4jpbj4NZ1h+DZNowLZsEAA) - [@tannerlinsley's case](https://www.typescriptlang.org/play?ts=4.7.4#code/GYVwdgxgLglg9mABCAzgUwIojQJwJ4A8AKlrngNJp4A0iRAIgIZSMB8AFAPpwAOsCKAFyIA3gChEiAI7Z8lPMJKyKVANwTpygGJhh7CAihoAHlAD8wkZrLzFpOVUQBfAJSIAvKzpMW6yQgBlEAgINBQhRHYAE2ZGRR9GN09EADc4GCj1V1EnMTEDMBQoawc8D0QAbQAiIyKq2gBGWgAmWisAZmEoHGxnAF08gHpBxDA4RAKjU1HxiHwxVExldnFJGRsqag11-B09F2EwEABbACNcDy8mjUDg0PC9GJYkryfGADooOC0YYzQo9guLaudRiYaIRgoRAoOAICFQgCSyHQEygxlob0QMChY0QABsEABzC5wYCIKB4HhoUYnc44RDAOD024hMIoBboex4FbbZTyLZrbS6SLQYwHGlnC7Ja6ScEAdQAFmVsYgAAZvVWIUnkynU1WMMB4VVmG5gIKsh6RN4vRBvT7fX7-QHAlyqIA) The issue can be closed.

As a workaround, this is what I do before loading Elk: ```ts (globalThis as any).g = undefined; (globalThis as any).i = undefined; ```

Roger that, although I think that the usual expectation in the npm ecosystem is to only bump the version in `package.json` just before making a release.

Since this has changed between 4.7 and 4.8 - is there any TS issue to track this specific regression/change on their side?

> If we treat the AST like a directed graph, then it's a matter of taking one extra "step" to find the source of the value, I agree that it's...

I wonder - have you tried pressing the autolayout button? It would be good to confirm if this is caused by a broken autolayout string (or incorrect handling of that...

Thank you for your report. I've found the VS Code APIs that we can use to fix this.