fix: use-deep-compare-effect

[missinglink]

resolves #27

the initial values for useDeepCompareEffect (when no additional HTML attributes are set) is equal to [string, nil, nil] which triggers the error mentioned in the GH issue.

the existing code spreads options, meaning it expects an object, this change simply ensures it is always an object, which placates the deps.every(isPrimitive) check in use-deep-compare-effect.

[missinglink]

TBH I'm still a little confused why the production build generated with npm run build works perfectly but the dev build using npm run dev fails.

I went over the scripts/*.js files and they seem to be basically identical, I also can't find anywhere which the environment is defined, either via ENV var or otherwise.

I suspect that it's something to do with error boundaries but don't see where that is defined either 🤷

[missinglink]

reviewed by @jedhastwell, thanks Jed! ☕