Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update dependency jotai to v2 #67

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update dependency jotai to v2 #67

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 31, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jotai 1.13.1 -> 2.8.3 age adoption passing confidence

Release Notes

pmndrs/jotai (jotai)

v2.8.3

Compare Source

The improvement for atomWithStorage in v2.8.2 contained a bug, which is fixed in this version.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.8.2...v2.8.3

v2.8.2

Compare Source

This fixes another edge case and improves utils for more flexibility.

What's Changed
New Contributors

Full Changelog: pmndrs/jotai@v2.8.1...v2.8.2

v2.8.1

Compare Source

This fixes a regression in v2.6.4 and a regression in v2.7.0.

What's Changed
New Contributors

Full Changelog: pmndrs/jotai@v2.8.0...v2.8.1

v2.8.0

Compare Source

v2.7.2

Compare Source

Mostly refactors.

What's Changed

Full Changelog: pmndrs/jotai@v2.7.1...v2.7.2

v2.7.1

Compare Source

This fixes a regression in v2.7.0.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.7.0...v2.7.1

v2.7.0

Compare Source

We've improved the use of WeakMap for better memory management. Please report to us if any regressions are found.

What's Changed

Full Changelog: pmndrs/jotai@v2.6.5...v2.7.0

v2.6.5

Compare Source

Some type improvements!

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.6.4...v2.6.5

v2.6.4

Compare Source

Performance improvement! Check it out!

What's Changed
New Contributors

Full Changelog: pmndrs/jotai@v2.6.3...v2.6.4

v2.6.3

Compare Source

Some improvements in core and utils 👏

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.6.2...v2.6.3

v2.6.2

Compare Source

Some improvements for atomWithStorage. Feedback is welcome.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.6.1...v2.6.2

v2.6.1

Compare Source

This version has two minor improvements for library authors. It's wonderful to see Jotai ecosystem growing. No major bugs have been reported lately. It's fairly okay to say the current version is pretty stable.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.6.0...v2.6.1

v2.6.0

Compare Source

We can now directly use <Provider> in React Server Components. 🎉

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.5.1...v2.6.0

v2.5.1

Compare Source

This fixes some small issues in jotai/utils.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.5.0...v2.5.1

v2.5.0

Compare Source

This fixes some bugs, one of which was critical for jotai-effect. It also adds a new internal capability that may help extensions such as jotai-scope.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.4.3...v2.5.0

v2.4.3

Compare Source

This fixes a regression in an edge case, which has existed since v2.1.1.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.4.2...v2.4.3

v2.4.2

Compare Source

There was a bug in v2.4.0 (and v2.4.1) in an edge case, which is now fixed.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.4.1...v2.4.2

v2.4.1

Compare Source

There was a regression in v2.3.0, which is fixed.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.4.0...v2.4.1

v2.4.0

Compare Source

This version fixes an edge case in core that has existed since v2.0.0.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.3.1...v2.4.0

v2.3.1

Compare Source

There was a bug in #​2061, which is fixed. It's about a dev-only warning.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.3.0...v2.3.1

v2.3.0

Compare Source

Jotai v2's store API is framework-agnostic. The primary use case is for React, but the store can be used for other frameworks. One of the difficulties was handling promises, and there has been unstable_unwrap util since Jotai v2.0.0. Now, it's considered stable and becomes unwrap util (see docs for details).

What's Changed

Full Changelog: pmndrs/jotai@v2.2.3...v2.3.0

v2.2.3

Compare Source

This comes with some small improvements.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.2.2...v2.2.3

v2.2.2

Compare Source

This includes some fixes for edge cases.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.2.1...v2.2.2

v2.2.1

Compare Source

This includes some improvements in jotai/utils. Especially, unstable_unwrap is getting to be stable.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.2.0...v2.2.1

v2.2.0

Compare Source

It includes a few improvements. Some utils are rewritten as there was a misconception when migrating from v1. ESM builds are optimized for Vite users.

Migration Guide for jotai/utils

atomWithDefault
// suppose we have this
const asyncAtom = atom(() => Promise.resolve(1))
const countAtom = atomWithDefault((get) => get(asyncAtom))
// and in component
const setCount = useSetAtom(countAtom)

// previously,
setCount((c) => c + 1) // it worked, but it will no longer work

// instead, you need to do this
setCount((countPromise) => countPromise.then((c) => c + 1))
atomWithStorage
// suppose we have async storage
const storage = createJSONStorage(() => AsyncStorage)
const countAtom = atomWithStorage('count-key', 0, storage)
  // in component
  const [count, setCount] = useAtom(countAom)

  // previously, countAtom is a sync atom, so you could update like this:
  setCount((c) => c + 1)

  // with the new version, it becomes async occasionally, so you need to resolve it:
  setCount(async (c) => (await c) + 1)

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.1.1...v2.2.0

v2.1.1

Compare Source

This version fixes some issues in edge cases.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.1.0...v2.1.1

v2.1.0

Compare Source

This includes some improvements as well as some breaking changes in unstable features.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.0.4...v2.1.0

v2.0.4

Compare Source

This includes some small improvements. One of them is to improve Deno compatibility.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.0.3...v2.0.4

v2.0.3

Compare Source

v2.0.2

Compare Source

This version add some small improvements, mostly for some minor cases.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.0.1...v2.0.2

v2.0.1

Compare Source

This adds various small improvements. Docs are also updated.

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v2.0.0...v2.0.1

v2.0.0

Compare Source

🎉 🎉 🎉 Jotai v2 is here! 🍾 🍾 🍾

Backward compatible for JS users without async atoms

Async atom behavior is revisited and changed. TypeScript types are changed and improved.

New Store API

Exposes createStore which opens up new usages. With its power, it can be misused. Let's look for best practice. Feedback is appreciated.

Migration Guide

https://github.com/pmndrs/jotai/blob/v2.0.0/docs/guides/migrating-to-v2-api.mdx

What's Changed

New Contributors

Full Changelog: pmndrs/jotai@v1.13.1...v2.0.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Jan 31, 2023 •
edited

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
lens-demo-app ❌ Failed (Inspect) Jun 3, 2024 3:08pm

@changeset-bot
Copy link

changeset-bot bot commented Jan 31, 2023 •
edited

⚠️ No Changeset found

Latest commit: dafb3bd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security
Copy link

socket-security bot commented Feb 9, 2023 •
edited

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

@socket-security
Copy link

socket-security bot commented Jun 12, 2023 •
edited

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/jotai@2.8.3 None 0 0 B

🚮 Removed packages: npm/jotai@1.13.1

View full report↗︎

@vercel Vercel
Copy link

vercel bot commented Nov 5, 2023

Deployment failed with the following error:

Resource is limited - try again in 26 minutes (more than 100, code: "api-deployments-free-per-day").

@coderabbitai coderabbitai
Copy link

coderabbitai bot commented May 22, 2024 •
edited

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants