Found a problem when using jsdom in a Jenkins environment, where our workspaces often have spaces in the filenames.
When the path to a script has spaces in its filename they are swapped with "%20"s by URL.resolve(). That's not a problem in itself, but when core.resourceLoader.readFile tries to pull the file off disk it fails with an ENOENT.
Fixed bug where script passed to jsdom.env contains spaces
Nice find, thanks.