Rename the project due to popular demand

[kripod]

As discussed on Reddit, the word "standard" may confuse some users:

Seeing the word "standard" in the name gives me flashbacks of the so-called "standard" config for ESLint which was not at all standard and quite opinionated in parts. – qeBhuajX5JAooqbRNiNv

I am open towards further discussion, listening to any viable alternatives which would eliminate bad feelings related to branding. The only requirement is that the name has to be generic enough to cover all the aspects of the library.

[moljac024]

• pocket-hooks
• swiss-army-hooks
• kitchen-sink-hooks
• kitchen-hooks
• hooksorama
• hooks-and-beyond

[fmoliveira]

browser-api-hooks ¯\_(ツ)_/¯

[srdjan]

"Essential set of React Hooks for convenient Web API consumption." =>
web-api-hooks
react-web-api-hooks

[Jose4gg]

hooky

[JoseRFelix]

utility-hooks

[kripod]

Thanks for all the suggestions! There is a discussion over Reddit with some interesting suggestions. I'm considering to split the package in half, providing:

• Web API hooks
• State hooks

In the form of a monorepo.

[fmoliveira]

I think that split makes a lot of sense @kripod !

[kripod]

The transition to a monorepo-based structure will be aligned with the release of v2. The package standard-hooks is going to be deprecated in favor of:

• web-api-hooks – sensor, storage and scheduling-related, specification-dependent hooks
• state-hooks – custom utilities for state management

In order to avoid confusion between versions, both packages will begin with v2.0.0, while no new major release is going to be published under the name standard-hooks.

[kripod]

Version 2 has been officially released, with changelogs available for web-api-hooks and state-hooks. Thanks for the overwhelming support I got from everyone!