Skip to content

feat: Rename NuxtUI extension to just Nuxt#17751

Closed
HugoRCD wants to merge 4 commits intoraycast:mainfrom
HugoRCD:ext/nuxt
Closed

feat: Rename NuxtUI extension to just Nuxt#17751
HugoRCD wants to merge 4 commits intoraycast:mainfrom
HugoRCD:ext/nuxt

Conversation

@HugoRCD
Copy link
Contributor

@HugoRCD HugoRCD commented Mar 11, 2025

Description

Screencast

nuxt-1
nuxt-2
nuxt-3
nuxt-4

Checklist

The aim of this PR is above all to rename the current extension (Nuxt UI) to (Nuxt) in order to extend its capabilities and no longer be simply limited to NuxtUI (we've discussed this directly with the Nuxt team (NuxtLabs)).

@raycastbot raycastbot added extension fix / improvement Label for PRs with extension's fix improvements extension: nuxt-ui Issues related to the nuxt-ui extension OP is author The OP of the PR is the author of the extension labels Mar 11, 2025
@raycastbot
Copy link
Collaborator

Thank you for the update! 🎉

Due to our current reduced availability, the initial review may take up to 10-15 business days

@HugoRCD HugoRCD changed the title feat: Rename NuxtUI extension to simply Nuxt feat: Rename NuxtUI extension to just Nuxt Mar 11, 2025
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

This PR renames the extension from "Nuxt UI" to "Nuxt" while significantly expanding its functionality to cover the entire Nuxt ecosystem, including module management and enhanced search capabilities.

  • Added new module-related tools (get-module-by-name, get-module-categories, get-modules-by-category) for exploring the Nuxt ecosystem
  • Added new search interfaces (search-components.tsx, search-modules.tsx) with filtering and category support
  • Introduced comprehensive TypeScript interfaces in types/modules.ts and types/components.ts for better type safety
  • Missing ai field in package.json despite having tools defined, should include evals from ai.yaml
  • Missing metadata folder for screenshots since there are view commands in package.json

💡 (2/5) Greptile learns from your feedback when you react with 👍/👎!

19 file(s) reviewed, 21 comment(s)
Edit PR Review Bot Settings | Greptile

Copy link
Contributor

@LitoMore LitoMore left a comment

Choose a reason for hiding this comment

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

You can consider renaming the extension folder from nuxt-ui to nuxt.

@HugoRCD
Copy link
Contributor Author

HugoRCD commented Mar 11, 2025

@LitoMore But will people who have installed the NuxtUI extension automatically get the Nuxt extension?

@LitoMore
Copy link
Contributor

I'm not sure but this should be fine. See the related discussion on Raycast Slack: https://raycastcommunity.slack.com/archives/C02HEMAF2SJ/p1741416077182769.

@HugoRCD
Copy link
Contributor Author

HugoRCD commented Mar 11, 2025

Ok I'll do that then !!!

@HugoRCD
Copy link
Contributor Author

HugoRCD commented Mar 11, 2025

@LitoMore This should be good now ?

@pernielsentikaer
Copy link
Collaborator

So CI fails because there are two folders here, if you don't know how to fix it I suggest:

  1. First move everything 1:1 to the new folder and make a PR with that
  2. Edit your files after it's moved

Otherwise, see if you can get the other folder out of the scope here

@pernielsentikaer pernielsentikaer self-assigned this Mar 13, 2025
@HugoRCD
Copy link
Contributor Author

HugoRCD commented Mar 14, 2025

@pernielsentikaer Yes I can make a new PR but how does it work because I contacted support to find out if renaming the extension would affect people who already have it installed? Because I would like those who have installed it to just see the new name without having to reinstall it 🤔

@pernielsentikaer
Copy link
Collaborator

I'm the support

a-man-in-a-red-superhero-costume-stands-in-front-of-a-building

I can do the initial move to the new folder, and then we can handle the rest of the naming - everyone will receive the updates if done properly 😊

What should we move it to?

@HugoRCD
Copy link
Contributor Author

HugoRCD commented Mar 14, 2025

😂

I don't know if I understood what you meant or not. But the goal is to completely replace nuxt-ui (the current name) with Nuxt so as not to block the extension's progress to only Nuxt UI.

@pernielsentikaer
Copy link
Collaborator

I'm merging this soon: #17844 - this ONLY moves the files to a new folder, and then you can make your modifications 😊

@pernielsentikaer
Copy link
Collaborator

Now it's moved to the new folder, can you either correct this PR or update the extension from the store and fork that one?

@HugoRCD
Copy link
Contributor Author

HugoRCD commented Mar 15, 2025

Now it's moved to the new folder, can you either correct this PR or update the extension from the store and fork that one?

What do you mean by correcting this PR?

@pernielsentikaer
Copy link
Collaborator

Have you seen all the merge conflicts? Might be easier to make a new PR with correct edits

@HugoRCD
Copy link
Contributor Author

HugoRCD commented Mar 15, 2025

@pernielsentikaer Ah yes ok indeed, I'll open a new PR! 😁

@HugoRCD HugoRCD closed this by deleting the head repository Mar 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

extension fix / improvement Label for PRs with extension's fix improvements extension: nuxt-ui Issues related to the nuxt-ui extension OP is author The OP of the PR is the author of the extension

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants