This is great work! I am loving the new dev speed.
I am looking forward to restoring my client code back into Meteor’s control sometime (for now I compile it separately and place it in the meteor app using a separate step from Meteor, to avoid issues Meteor had with dependencies and basically to have full control in a simple way).
CSS has and is evolving a lot. I really don’t see SCSS being necessary as a default that requires learning a new language. CSS today has:
- variables
- nesting
- functions and mixins
- donut scopes with @scope
- layers
- native CSS Modules (import them into JS!)
if()logic- native scoping via ShadowDOM
- plus more today
- and more coming soon!
For browsers that don’t support the latest features yet, we can use PostCSS preset-env to compile new CSS to old CSS, and be aligned with modern standards.
Unless a CSS alt languages like SCSS or LESS provide a substantial benefit over native CSS, including making it worth new code deviating from standards evolution and the future debt that may add, and considering that CSS has caught up to the features of SCSS or LESS, I don’t see a big benefit defaulting to SCSS or LESS.
I really want to see a fully standards-aligned Meteor, with everything else optional to opt into.