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

Default pre-processor language #4320

Closed
sebmor opened this issue Nov 12, 2018 · 3 comments
Closed

Default pre-processor language #4320

sebmor opened this issue Nov 12, 2018 · 3 comments

Comments

@sebmor
Copy link

sebmor commented Nov 12, 2018

What problem does this feature solve?

Currently, if you use a certain pre-processor (cfr.
https://nuxtjs.org/faq/pre-processors/), you most likely use it predominantly in your app. It would potentially make sense to have the option to declare a default so you don't have to repeat yourself. Of course always possible to be overridden on a per component basis.

For example; I use in every component <style lang="scss">. This could be a setting in nuxt.config instead and I could default to <style>.

I think of it kind of similar to how currently transition is implemented, there is a default config available in nuxt.config, but you can also set per component transitions. (cfr. https://nuxtjs.org/api/configuration-transition#the-transition-property & https://nuxtjs.org/api/pages-transition#the-transition-property)

What does the proposed changes look like?

Something along the lines of:

module.exports = {
  preprocessors: {
    style: scss
 }
}
<style scoped>
</style>
This feature request is available on Nuxt community (#c8128)
@ghost ghost added the cmty:feature-request label Nov 12, 2018
@simonhermann
Copy link

That'd be nice, but how would your text editor know that you use scss?

@manniL
Copy link
Member

manniL commented Nov 25, 2018

This might be a better issue for vue-loader instead ☺️ (rel: vuejs/vue-loader#500).

@manniL manniL closed this as completed Nov 25, 2018
@lock
Copy link

lock bot commented Dec 26, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants