@redmunds The `FileSystem` APIs all _only_ work with paths -- if someone passes in a URL, they will all fail.  I don't think we should change this one API to accept URLs when none of the other related APIs do.

Where is the path originating from in this case?  It seems like it's part of Require.  If Require has a feature/bug where it sometimes passes `file://...` URLs and sometimes passes absolute Linux/Mac system paths, then it seems appropriate to me to place a workaround specific to that issue localized in this one bit of code that actually interacts with those Require APIs.