#Nuxt UI documentation

11 messages Β· Page 1 of 1 (latest)

fading sleet
#

Hello πŸ‘‹

Got confused by the Nuxt UI docs (ui.nuxt.com) and wanted to know if it happened to others.

Context: integrating UFileUpload for the time.
Problem: it broke the tab navigation.
Confusion: (see screenshot) the docs said it was already fixed.
Clarification: Fixed in the repo yes but not yet released (not in 4.0.1)
Details:


I integrated the code fix in a pnpm patch for now. so I should be alright until the next release. Let me know if you have been confused by the docs before. πŸ™‚

GitHub

πŸ”— Linked issue
Resolves: #5102

❓ Type of change

πŸ“– Documentation (updates to the documentation or readme)
🐞 Bug fix (a non-breaking change that fixes an issue)
πŸ‘Œ Enhancement (improving an exis...

GitHub

πŸ› Bug Fixes

App: allow global portal disabling (#5111) (7659fa1)
AuthForm: export type with proper inference for field-specific props (#5106) (344f269)
Avatar: remove redundant img role (066b8a1),...

raw gulchBOT
#

Hi @fading sleet. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

You're correct in your understanding: the fix for the tab navigation issue in UFileUpload (PR #5128) is listed in the Nuxt UI documentation changelog, but it has not yet been included in an official release such as v4.0.1. The changelog for the FileUpload component specifically mentions this fix:

2477d β€” fix: stuck focus while tabbing (#5128)
See changelog

However, if you check the v4.0.1 release notes, this PR is not included, which means the fix is present in the main branch but not yet published in a stable release. This can indeed be confusing, as the documentation reflects the latest changes in the repository, not just what is available in the latest npm release.

For cases like this, Nuxt UI supports installing preview releases directly from a commit using pkg.pr.new. This allows you to use the latest fixes before they're officially released:

{
  "dependencies": {
    "@nuxt/ui": "<https://pkg.pr.new/@nuxt/ui@<commit-hash>">
  }
}

Replace <commit-hash> with the hash of a commit that includes the fix.

#

Your approach of using a patch is a good workaround until the next official release. This kind of confusion can happen because the docs are always up-to-date with the main branch, not necessarily with the latest published version. You're not alone in noticing this!
Nuxt UI FileUpload Changelog
Nuxt UI Continuous Releases

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@fading sleet Kapa.ai is still learning and improving, please let me know how I did by reacting below.

fading sleet
#

My opinion is the following: When reading the docs, I think it should be safe to assume that what is mentioned in the changelog is included in the latest stable release. πŸ™‚

tacit tendon
#

I agree with you, @fading sleet

#

Can we discuss about this in detail?

fading sleet
#

@tacit tendon sure. How can I help?

tacit tendon
#

Did you already fix the nuxt project issues?
I just wanted to help you solve the issue

#

Are you a member of the nuxt core dev team?