Added some guards to keep execution in a node context from throwing ReferenceErrors

[swansong]

My team is using react-filepond in a React UI kit, and we love it! There's one issue we ran into with server-side-rendered applications that imported our implementing component: we'd get ReferenceErrors for performance, window and document. These guards here make it so our component renders fine on the server and works in the browser.

[swansong]

sorry something is up with this, gonna close until I have it sorted

[rikschennink]

@swansong Thanks for reporting! If I understand correctly the navigator object is available on your node instance? Maybe it's defined by another module?

I found this Stack Overflow answer that can help detect a browser environment, I like the solutation so will probably go with that:
https://stackoverflow.com/a/31090240/1774081

As the source is not in the repository yet I'll make the changes to the source files and publish a new version later this week or at the start of the next.

[rikschennink]

@swansong I've updated the code with this check

const isBrowser = new Function('try {return this===window}catch(e){return false}');

Will publish a new version later today. Unfortunately, the source files are not in the repo just jet so I'll have to close the pull request.

[rikschennink]

Just published version 2.3.0