Skip to content

Conversation

@ShayanTheNerd
Copy link
Contributor

I accidentally stumbled upon the documentation page for no-async-in-computed-properties rule, and noticed that it suggests using vue-async-computed package in case we need async code in computed. This package hasn't been maintained for over 2 years, so I believe computedAsync from VueUse is a much better, well-maintained alternative. Besides, there's a good chance that developers already use some other composable from VueUse, which means they won't need to install yet another random NPM package to solve a simple issue.

@changeset-bot
Copy link

changeset-bot bot commented Nov 26, 2025

⚠️ No Changeset found

Latest commit: 7024026

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

Copy link
Member

@FloEdelmann FloEdelmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me, thank you 🙂

@FloEdelmann FloEdelmann merged commit 9e4dde2 into vuejs:master Nov 27, 2025
15 checks passed
@FloEdelmann FloEdelmann changed the title Suggest computedAsync instead of 'vue-async-computed' docs(no-async-in-computed-properties): suggest computedAsync instead of vue-async-computed Nov 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants