Sergii Lavrin

Well, I'd rather drop mixins altogether. And instead have a function, which could return CSS fragments and thus act as mixins. So, instead of this: ```scss @mixin borders ($value) {...

To be honest, CSS fragments from https://github.com/sass/sass/issues/1582#issuecomment-72259831 blowed my mind. In a bad way. `()` instead of `{}` and `[]` for maps _and_ arrays notation didn't help it too... Those...

Just for the information, I posted some related ideas in #2252

@DonGissel good point, I was thinking about exactly same thing some time ago. Btw, it needed not only to save few bytes. According to latests Google Lighthouse requirements, it is...

Worth to mention [JSPM](https://jspm.io/) and [SystemJS](https://github.com/systemjs/systemjs) (that's what JSPM uses under the hood) to the list. SystemJS implements ES module specs — what some modern browsers already supporting — so...

Also worth to check how it's done in [Babel](https://babeljs.io/docs/usage/babelrc/), [ESLint](https://eslint.org/docs/2.0.0/user-guide/configuring), [Stylelint](https://stylelint.io/user-guide/configuration/) and [Jest](https://facebook.github.io/jest/docs/en/configuration.html)

My two cents into why nor mixins, nor attempts to define what actually should be imported outside of Sass won't be enough. For instance, let's take some complex web-projects, build...

In my case, it works unless async actions are using. Seems like only sync operations are applied

It's most likely upstream issue. Did you try to test it with native lodash `_.template(...)`? Does it produce those slashes too?

Oh, now I see why it doesn't work. Here is example from docs: ``` js // Use backslashes to treat delimiters as plain text. var compiled = _.template(''); compiled({ 'value':...