Make the lib at least partially browser compatible

[meszaros-lajos-gyorgy]

[meszaros-lajos-gyorgy]

Some sort of loader is needed within the platform folders for loading files. The node version could use the fs module, while the browser could load from an ArrayBuffer or do a fetch call.

[meszaros-lajos-gyorgy]

10 more files to go: either have to move them to src/platform/node and then create a browser counterpart + common interface or replace node specific functions with custom functions, like how I already did for most of path.resolve and path.join:

[meszaros-lajos-gyorgy]

I have to admit defeat, this is impossible to do, at least for now. The final nail in the coffin was when I tried splitting Texture into a browser and node variant while trying to create a common interface for them. Texture is one of those classes that have a lot of static methods as alternatives for constructors, like Texture.fromCustomFile(). You can't have a static property or method for an interface and you can't have an abstract static method for a class.

[meszaros-lajos-gyorgy]

Instead of trying to give a class to ArxMap to handle platform specific stuff it seems a better solution to do things the other way around. I'm re-opening the ticket as I made a tiny bit of progress and it seems more doable now.

[meszaros-lajos-gyorgy]

Things that are heavily node dependant have been moved to @platform/node and not all of them will have a browser counterpart.