Github

> Could you give an example of how your file is currently formatted? > Yes, I just tried changing the file path to exactly match the compiler output error, this...

> Does this work? > > ``` > swit/js/swit/phys/PhysBody.js:9 Bad type annotation. Unknown type XYZ > ``` No luck, I tried with (?) character also. For the record the class...

> Can you try pasting the warning message from JSCompiler exactly how it appears. i.e. `swit/js/swit/phys/PhysBody.js:9:13: WARNING - [JSC_UNRECOGNIZED_TYPE_ERROR] Bad type annotation. Unknown type XYZ` I remember I tried that,...

I was having this issue on my old node backend, I updated everything and still had the error, turns out I'm an idiot and was forcing the system to use...

I feel JS is too slow for this, I found a C++ native tool for this, thanks

> @bamtang-dev can you tell me what tool it is? https://github.com/NPP-JSONViewer/JSON-Viewer

@AshleyScirra we also found that using the Closure Compiler outside of the path that is used inside Google is a BAD IDEA, I found some real issues with our code...

the thing that I'm missing the most is dead code removal, even TypeScript that has all the information to do this prefers not to do it, but well, maybe they...