[Proposal] Set target to ES5

Have you considered changing the build target to ES5 instead of ES6 so that this library works across more browsers?

Alternatively, you can ship 2 different builds (one with target=ES5 and one with target=ES6), I’ve seen some other libraries do this and then as a client, I could do import useLocalStorageState from "use-local-storage-state/es5".

[astoilkov]

@callumlocke @Luccasoli This issue is not related to the ES5 target. I created a new issue for that – #20. I fixed the issue in a new 8.0.0 release. You can upgrade now but you should do it manually because the ^7.0.0 constraint doesn’t allow it.

[astoilkov]

I thought a lot about this. I decided to not add support for ES5. These are my arguments:

• ES5 is an edge case. I don’t know how much but I believe there is a very small amount of users that need this. IE takes 0.8 percent of the market share.
• It’s not a deal-breaker. Users can still use @babel to transpile this module to ES5. This solution will be increasingly more popular as more modules don’t support ES5.
• The trend I am trying to follow is forward not backward. I am currently shipping two versions of the package: non-ESM and ESM and it’s overly complicated. I will be soon shipping only ESM(same as Sindre Sorhus). This will probably get even more users mad but this will push the ecosystem further.
• It adds complexity to the codebase. I am obsessed with code complexity and this will add an additional step to the build process and complicate it. I don’t like that.