:rotating_light: The automated release from the master branch failed. :rotating_light:

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

What is the current behavior? I've got an error

node_modules/react-use/lib/useGeolocation.d.ts(11,21): error TS2304: Cannot find name 'PositionError'.

react-use: 15.3.4 typescript: 4.1.2

What is the current behavior? [1/4] 🔍 Resolving packages... error Couldn't find package "@xobotyi/[email protected]" required by "react-use" on the "npm" registry. info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Steps to reproduce it and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have extra dependencies other than react-use. Paste the link to your JSFiddle or CodeSandbox example below: none What is the expected behavior? Install it A little about versions:

• OS: Mac OS 10.15.6
• Browser (vendor and version): Chrome 84.0.4147.105
• React: 16.10.0
• react-use: 15.3.3
• Did this worked in the previous package version? no

useAsyncFn and useAsync typings made great again =)
Now it uses fully generic arguments and returning types, thus no problems with inferring callback arguments and value types;

PS: @streamich check the #381 PR too.

since update to react 16.8.2 useSetState doesn't work

https://streamich.github.io/react-use/?selectedKind=State%2FuseSetState&selectedStory=Demo&full=0&addons=1&stories=1&panelRight=0

I’ve enabled the strict option in my tsconfig.json, and installing this package results in an error because it can’t find types for the useCallbag hook, even though I don’t use that hook. It seems to be trying to import the types for the use-callbag package, which don’t exist. Can you fix this error?

Problem

const [registration, register] = useAsyncFn(Service.register)

async function handleSubmit(){
  try {
    await register(payload)
    // it always succeeds
  } catch(error){
    // it never reaches here
  } 
}

Why the get, set, remove and remove functions are not wrapped in useCallback?

https://github.com/streamich/react-use/blob/master/src/useMap.ts

The same question applies to functions returned by useList.

Description

This PR addresses https://github.com/streamich/react-use/pull/2080#pullrequestreview-743239467.

The yaml is inspired by gicentre/prettier-plugin-elm → .github/workflows/check-codebase.yml.

Type of change

• [ ] ~~Bug fix (non-breaking change which fixes an issue)~~
• [ ] ~~xNew feature (non-breaking change which adds functionality)~~
• [ ] ~~Breaking change (fix or feature that would cause existing functionality to not work as before)~~
• [x] Chore (CI updates)

Checklist

• [x] Read the Contributing Guide
• [x] Perform a code self-review
• [x] Comment the code, particularly in hard-to-understand areas
• [ ] ~~Add documentation~~
• [ ] ~~Add hook's story at Storybook~~
• [ ] ~~Cover changes with tests~~
• [x] Ensure the test suite passes (yarn test)
• [ ] ~~Provide 100% tests coverage~~
• [x] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
• [x] Make sure types are fine (yarn lint:types).

What is the current behavior?

As of #1295 (v15.3.0), if React renders a component twice before committing (as it does to every component in the excellent <React.StrictMode>, and apparently as CodePen does even without StrictMode), the second render will get a prematurely updated value. The React docs (which the react-use docs references) uses useEffect for this reason. That PR should be reverted. 😞

Steps to reproduce it and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have extra dependencies other than react-use. Paste the link to your JSFiddle or CodeSandbox example below:

Use <StrictMode> to turn on double-rendering. Use usePrevious. Note that on the second render, the usePrevious value is from the first (duplicate, discarded) render, not from the previous commit. This means that, for the render which ends up getting committed, the usePrevious value that ends up reflected in the DOM is always the current one, not the previous one.

What is the expected behavior?

The previous value should not update until after the render is committed, via useEffect.

A little about versions:

• OS: n/a
• Browser (vendor and version): n/a
• React: n/a
• react-use: 15.3.0
• Did this worked in the previous package version? Yes, until #1295 and v15.3.0.

Addresses #785

Description

Basically a total rewrite of useLocalStorage to ensure updates to the keyed value are picked up by all components watching for it.

Type of change

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as before)

I don't believe this will cause any breaking changes. But I did end up tearing out almost all the old code and fundamentally changed how this hook works. 🤷‍♂

Checklist

• [x] Read the Contributing Guide
  • [ ] better commit message
  • [ ] squash?
• [x] Perform a code self-review
• [x] Comment the code, particularly in hard-to-understand areas
• [x] Add documentation
  • no changes
• [x] Add hook's story at Storybook
  • no changes
• [x] Cover changes with tests
• [x] Ensure the test suite passes (yarn test)
• [x] Provide 100% tests coverage
• [x] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
• [x] Make sure types are fine (yarn lint:types).
  • Could use more input for proper types, like raw=true implies value=string

Description

Fix the type error when using useMeasure

Type of change

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as before)

Checklist

• [x] Read the Contributing Guide
• [x] Perform a code self-review
• [ ] Comment the code, particularly in hard-to-understand areas
• [ ] Add documentation
• [ ] Add hook's story at Storybook
• [ ] Cover changes with tests
• [x] Ensure the test suite passes (yarn test)
• [ ] Provide 100% tests coverage
• [x] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
• [x] Make sure types are fine (yarn lint:types).

Description

A React hook that creates a globally shared state via useSyncExternalStore. It supports performance optimization through the selector function, and will only re-render when the subscribed data changes

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as before)

Checklist

• [x] Read the Contributing Guide
• [x] Perform a code self-review
• [x] Comment the code, particularly in hard-to-understand areas
• [x] Add documentation
• [x] Add hook's story at Storybook
• [x] Cover changes with tests
• [x] Ensure the test suite passes (yarn test)
• [x] Provide 100% tests coverage
• [x] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
• [x] Make sure types are fine (yarn lint:types).

Description

Make useMethods consistent with both useState and useReducer by not updating the returned methods object reference if initialState changes after the initial render:

The initialState argument is the state used during the initial render. In subsequent renders, it is disregarded.

— reactjs.org/docs/hooks-reference.html#lazy-initial-state

Closes #1286

Type of change

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as before)

Checklist

• [x] Read the Contributing Guide
• [x] Perform a code self-review
• [x] Comment the code, particularly in hard-to-understand areas
• [ ] Add documentation
• [ ] Add hook's story at Storybook
• [x] Cover changes with tests
• [x] Ensure the test suite passes (yarn test)
• [x] Provide 100% tests coverage
• [x] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
• [x] Make sure types are fine (yarn lint:types).

What is the current behavior?

useCustomCompareEffect does not give a chance to prevent running the effect on mount. The code says that depsEqual are not even called, as first part of !ref.current || !depsEqual(deps, ref.current) expression is falsy.

What is the expected behavior? depsEqual should be called to allow deciding on not running the effect on mount, as for every later state change.

A little about versions:

• OS: Linux
• Browser (vendor and version): Firefox
• React: 18.2
• react-use: 17.4.0
• Did this worked in the previous package version?: I don't think so.

Description

I believe that using useEffect can lead to race conditions. Since the event is subscribed asynchronously, it can be missed or use an incorrect handler. See also:

• https://stackoverflow.com/questions/68407187/potential-bug-in-official-useinterval-example *https://stackoverflow.com/questions/74835264/avoiding-race-conditions-with-react-hooks-and-native-callbacks/74835303#74835303

Type of change

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as before)

Checklist

• [ ] Read the Contributing Guide
• [ ] Perform a code self-review
• [ ] Comment the code, particularly in hard-to-understand areas
• [ ] Add documentation
• [ ] Add hook's story at Storybook
• [ ] Cover changes with tests
• [ ] Ensure the test suite passes (yarn test)
• [ ] Provide 100% tests coverage
• [ ] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
• [ ] Make sure types are fine (yarn lint:types).