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

Maybe can provide an option to choose less/scss... #63

Open
btea opened this issue Feb 18, 2022 · 3 comments
Open

Maybe can provide an option to choose less/scss... #63

btea opened this issue Feb 18, 2022 · 3 comments
Labels
documentation Improvements or additions to documentation

Comments

@btea
Copy link
Collaborator

btea commented Feb 18, 2022

Hello, the current project basically uses the CSS extension language to write styles, so I think that might be good to provide an option to choose to add it.

What do you think?

@tarunama
Copy link

tarunama commented Jul 4, 2022

This is just needly option !

@stefnotch
Copy link

stefnotch commented Aug 16, 2022

Alternatively it might be worth integrating https://github.com/unocss/unocss as an option.

This was referenced Jul 28, 2023
@haoqunjiang
Copy link
Member

Thank you for your input.

I have some concerns about adding this option to the scaffold:

  1. Vite's Official Recommendation: Vite encourages using modern CSS features instead of these preprocessors. It's because Vite is designed for modern browsers, so it's better to use plain CSS with some helpful tools like postcss-nesting. This way, you're writing future-proof CSS. You can read more about this in the Vite documentation.

  2. Simplicity: You can actually use these preprocessors with Vite quite easily, and there's a guide in the Vite documentation that shows you how. So, adding them to our templates might not bring much extra value, but it could make maintenance more complicated.

  3. Performance Concerns: Some of these preprocessors, like less, can slow down your project without offering many extra benefits. If you don't really need them, it's best to stick to regular CSS.

  4. Tailwind CSS: In terms of popularity, 'less' and 'stylus' have been less popular than Tailwind CSS for a while (you can check here). However, Tailwind CSS already has its own scaffold (https://tailwindcss.com/docs/guides/vite#vue), so there's no need to duplicate the effort here.

Considering these points, I don't think adding another option to create-vue is the right move. But I'm open to the idea of improving our documentation to help users with CSS-related issues.

@haoqunjiang haoqunjiang added the documentation Improvements or additions to documentation label Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants