Behavior when loaded with node is confusing about fitty

[timseverien]

It was really confusing to me when, separately, I wasn't able to get the import working as expected.

@searls I'm curious: what did you expect what would happen when importing a browser library in node?

[searls]

The same functions to be there, regardless of whether they worked. For example, I'd bail at the last possible moment, and not at require-time. Maybe a user will require jsdom right afterward only to find fitty is {default: undefined} instead of {default: function thisWillBlowUpWithoutADom(){}}.

[rikschennink]

@searls happy to merge any pull requests that fix this

[godhandkiller]

@searls So how did you import the library to your project? I'm not able to do it

[EarthlingDavey]

If you can use imports... import fitty from 'fitty'; works for me.

[rikschennink]

Closed because inactive