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

feat: add option to keep default Import alias of create-next-app #1874

Closed
Parth589 opened this issue May 8, 2024 · 2 comments
Closed

feat: add option to keep default Import alias of create-next-app #1874

Parth589 opened this issue May 8, 2024 · 2 comments
Labels
🌟 enhancement New feature or request

Comments

@Parth589
Copy link

Parth589 commented May 8, 2024

Is your feature request related to a problem? Please describe.

I personally use create-next-app import alias @/* alot in my projects. shadcn/ui is also an important tool in my recent projects. i dont want to change the pasted code from templates. it's so annoying to everytime change the import statements just for an alias.

Describe the solution you'd like to see

just add an option to keep the import alias to @/ . i am tired of writing that while initializing all new projects.

Describe alternate solutions

You can just remove the ~/ alias from this project so everyone could be happy. (no offence but it's my personal opinion)

Additional information

No response

@Parth589 Parth589 added the 🌟 enhancement New feature or request label May 8, 2024
@afonsopimenta
Copy link
Contributor

@Parth589 You can just write @/ when it prompts for what import alias you'd like to use when initializing a project.

@juliusmarminge
Copy link
Member

juliusmarminge commented May 17, 2024

yea this issue makes no sense. No matter what default we pick, some are gonna argue for another one. It's not a lot of work for you to just write @/ when it prompts you.

We could also store your "preferred" setting in some global store (I think create-next-app does this) but that's a bigger task, although I'd be open for it! (open a new issue outlining this if so)

But we settled on the current default after a community vote so we're not gonna change it just cause of individuals personal prefrence.

@juliusmarminge juliusmarminge closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌟 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants