Recently, I've been developing a compact "library" for handling Http requests in TypeScript. The main component of this library is the Http class. After compiling my code into an es5 bundle using gulp-tsify, I wanted to ensure that the class could be accessed globally without manually rewriting the bundle script.
The issue arises when the compiled TypeScript outputs code within a self-invoking function scope, making it challenging to access the Http class outside of that scope. Manually manipulating the bundle script can solve the problem temporarily, but I was seeking a more automated solution.
My goal was to have the Http class automatically available as a global object upon compilation, without any manual intervention. I considered using something like declare var http = Http; directly in TypeScript, but encountered limitations due to restrictions on initializers in ambient contexts.
If you have any insights or suggestions on how to achieve this seamless integration of the Http class as a global entity, I would greatly appreciate your input. Thank you.