#2.5 / 4 rate

TypeScript Console

470 users

2024-09-09

rxliuli

[email protected]

Extension Information

5 star

25%

4 star

3 star

25%

2 star

1 star

50%

Supported Languages

Description

Run and debug TypeScript code in the Chrome DevTools.

Reviews

Ze*****

not working offering nothing ------- thanks to your collab this can be saved -- I will update it to 5 stars if you complete an update that addresses current bugs per se : can run it everywhere & extension not "disabled" ===== I will deeply respect you if you make your extension holistic to the console; doing a console override just to run TS normally as it would run any JS. -- But there's a lack of professionalism for saying I'm stating nonsense on GitHub while I sent you a real screenshot of what I did without relying on extensions and by solely reversing, although visual is easy compared to the core. In the past, I, by chance, was able to run TS into JavaScript, but that was probably a hidden feature or a bug that didn't enforce only JS. Aside from parsers who deflect the main issue; the theory of compilation addresses these problems & how they can be easily solved even though this transliteration isn't a compilation; the automata logic persists & it's possible to draw the **garbage throw** & through that you can establish your entry points of how you would redirect the garbage recollection & remake your own version garbage collection by adding or modifying the design assuring your automata is optimized to the way you wished; working as desired no longer throwing. This is about obvious reverse engineering, obviously something you never attempted; it would be the same as bypassing security mechanisms but way easier by creating a paradigm; similar to jailbreaking but way easier. You just have to redirect or override logic. I want to add that, thanks to your extension, you easily inject this, easily mimicking reverse engineering. You simply, through the console, make logic that handles code before the native handlers. To do this, you modify the native mechanism & replace it with a mechanism that makes you handle the input first, then address handling. In your primacy handling, you use your extension work as a holistic code to the problem that directly translates TS & runs it. This way, you have run TS in the console & circumvented the errors or garbage throwing that normally would not enable you to proceed. Thanks to your already implemented solution you can directly tweak the console & make this "extension" a console override that enables TS without any external visuals or unnecessary views. You can even handle your extension's only errors directly in the console.