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.

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

[bug]: /docs/components/rainbow-button #375

Open
nmrisrl11 opened this issue Oct 14, 2024 · 3 comments
Open

[bug]: /docs/components/rainbow-button #375

nmrisrl11 opened this issue Oct 14, 2024 · 3 comments

Comments

@nmrisrl11
Copy link

Describe the bug
I'm trying to install rainbow-button using CLI on my NextJS app.

My current folder structure:
src/app/[locale]/globals.css

I think by default when installing some MagicUI component this is all fine when there's no need to do some adjustments specially on globals.css.

But on my case with my current folder structure this will results an error because the current globals.css will not be found.

I know I can just manually just update some of my codes to make it work. But it would be better if the CLI installation setup can be flexible no matter where the globals.css file is. (is it possible?)

To Reproduce
Steps to reproduce the behavior:

  1. Install rainbow-button using CLI (must be the same folder structure with me)
  2. Just scroll down to see the error

Expected behavior
Just like other MagicUI components, ready to use just using CLI.

Screenshots
image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Brave
  • Version: 1.70.126
@nav2924
Copy link

nav2924 commented Oct 15, 2024

You can temporarily move or create a copy of your globals.css file at the default expected location (src/globals.css) before running the installation. After the installation, you can move the file back to its original location or manually update the references in the installed package.

@nmrisrl11
Copy link
Author

You can temporarily move or create a copy of your globals.css file at the default expected location (src/globals.css) before running the installation. After the installation, you can move the file back to its original location or manually update the references in the installed package.

Nice and yes this work around will work as well. But my concern here is it would be better if the installation of component (i.e. rainbow-button) will be done with just CLI. No need to do some extra steps, if the case is like mine.

@amyssnippet
Copy link

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants