FileLoader: Support environments without ReadableStream

[gkjohnson]

Related issue: #23015

Description

Adds a check to FileLoader to skip using ReadableStream and response.body.getReader if they are not supported by the current environment. Both of these were only added to Firefox within the last couple years and it seems most polyfills do not provide support for these, either.

With this change you can use the node-fetch package to enable FileLoader in node environments:

import { OBJLoader } from './examples/jsm/loaders/OBJLoader.js';
import fetch, { Request, Response, Headers } from 'node-fetch';

global.fetch = fetch;
global.Request = Request;
global.Response = Response;
global.Headers = Headers;

new OBJLoader()
  .loadAsync( 'https://raw.githubusercontent.com/mrdoob/three.js/dev/examples/models/obj/tree.obj' ).then( res => {

    console.log(res);

  } );

This doesn't completely address the react-native case, though. In order for that to be fixed FileReader.readAsArrayBuffer must be implemented in react native because it's used by the fetch polyfill they're depending on. facebook/react-native#30769 has implemented the function but unfortunately it's gotten no attention from the project.

cc @CodyJasonBennett

[CodyJasonBennett]

Thanks for the follow-up.

Yes, there's nothing more to do on our side for react-native, but it'll work OOTB with a few pending fixes. They can use r133 in the meantime.

I tested this locally on Node with a few setups, and it works nicely. Users should still try to avoid SSR with loaders that require browser APIs, so nothing's new there.

[mrdoob]

Thanks!