Fix issue with fast-deep-equal when used with Vite

[valtism]

When running this library from Vite, because it is ESM-only it will throw when trying to call equal from the fast-deep-equal library.

I believe this has to do with how it is imported, so we change the import * as equal from... to import equal from... and allow esModuleInterop in the .tsconfig

The output of this now works in a vite environment, and solves issue:
gilbarbara/react-joyride#769

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 659de4c:

Sandbox	Source
gilbarbara/tree-changes	Configuration

[valtism]

I'm not entirely sure of the implications of importing the way I did, or of enabling esModuleInterop, but this does seem to work for both create-react-app as well as Vite in the debug repo: https://github.com/maltsev/react-joyride-debug

[gilbarbara]

@valtism In my experience turning on esModuleInterop in a library forces the hosting app/library to have the same configuration which is not a desirable option.

[valtism]

@gilbarbara Ah, I wasn't aware of that and that does sound pretty undesirable. I guess that means that this issue is blocked by epoberezkin/fast-deep-equal#105

[valtism]

Is there any way around this without fast-deep-equal exporting esm module builds?

[JimmyRowland]

Also need a walk around

[valtism]

@JimmyRowland Here's a workaround: gilbarbara/react-joyride#769 (comment)

[JimmyRowland]

@valtism Thanks. The walk around seems to work. I am using react-floater and after fixing fast-deep-equal/deepmerge import, react-floater still doesn't show custom body component. I will have to give up

[gilbarbara]

Fixed in 0.9.0