gustavwilliam
commented
2 months ago @Flosciante from my debugging efforts, I can't isolate this PR as the cause of the warning. I'm getting the same warnings in the console when:
- Visiting a page without the new component, like http://localhost:3000/docs/getting-started/views
- Running the latest versions from before this PR (nuxt.com: bfae88ad, nuxt: 1e49d2c91)
At least this is what happens when I run it locally. Are you getting similar results?
Flosciante
🔗 Linked issue
Resolves nuxt/nuxt#28499
❓ Type of change
📚 Description
Adds a new content type in the docs for package manager instructions. When the user selects a package manager, the choice of package manager will be:
If the persisted package manager is not available for a given codegroup, the preference will default to
npm.All package manager code groups have been updated to the order npm -> yarn -> pnpm -> bun. An accompanying PR (nuxt/nuxt#28514) has been opened on nuxt/nuxt, to utilize this new
PackageManagerscomponent.Implementation choices
Watches exposed property
selectedIndexfrom the Nuxt UI ProCodeGroupcomponent. On selecting a new package manager, all package managers code groups will update instantly. This document-wide update is done using a document event listener. While a state management system like Pinia could be used to do this, I didn't find anything like that installed yet, and this small feature didn't justify adding the dependency in my opinion.In order to allow flexibility with what package managers are available, I opted to not implement automatic sorting of the available package managers in the code groups. Instead, the
PackageManagerscomponent dynamically gets the index of the persisted package manager. This means that regardless of the order of package managers passed to the component, the correct package manager will be selected.