I see. So, what’s happening is that your webserver that’s hosting the file is rejecting the Babylon Playground’s request to access the resource due to CORS policy. Basically, when the code you’ve written tries to fetch the resource, your webserver tries to confirm that the code sending the request was hosted by the same origin (i.e., your own webserver); and since it’s not, the webserver refuses to fulfill the request as a security policy because it doesn’t know that this request is trustworthy. To resolve this, you’d either need to set your webserver to allow this kind of request, run your Playground on the same webserver as your resource, or move your resource to a server that has CORS enabled.
If changing security policy on your webserver isn’t an option and you want to be able to test this locally (i.e., on your own computer with complete control), I’d recommend following the first two steps of this golden path to move your code and assets into local repos. The asset host described there is already set up for CORS, and moving the code will enable you to run your code in an HTTP site so that you can access the HTTP server into which you’ll drop your file. It takes a few steps, but it shouldn’t take much time, and it’s one of the simplest ways to set up a fully-controlled test environment without turning down security measures on your real webserver.
Hope this helps, and best of luck!