It's not quite there yet, but they've made a lot of progress in the last few months: https://github.com/sass/libsas...
It's not quite there yet, but they've made a lot of progress in the last few months: https://github.com/sass/libsass/wiki/The-LibSass-Compatibili... https://github.com/sass/libsass/milestones/3.2 http://sass-compatibility.github.io/ It's at the point where I can use node-sass and Ruby Sass interchangeably for our (very large) Sass code base at my company, but we also don't rely very heavily on the newest features. Worth a try, anyway. If node-sass doesn't work for you though, there's also a webpack loader for Ruby Sass: https://github.com/ddelbondio/ruby-sass-loader
Posted by peterjmag on Mar 9, 2015, 5:37 PM
Tags
Related issues
- That isn't really relevant for the tool starting the container.
- Why is there no link to the source?
- Something I wonder about in this domain is if this is the fault of the language.
- Namespace pollution is an annoying problem in Rust.
- Currently, no language ports of Timefold Solver are planned.
- I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Raise real-world problems, find people facing the same issue, and discuss solutions.7,500 issues0 comments
hackernews (Software)
That isn't really relevant for the tool starting the container.
Why is there no link to the source?
Something I wonder about in this domain is if this is the fault of the language.
Namespace pollution is an annoying problem in Rust.
Currently, no language ports of Timefold Solver are planned.
I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Why is there no simple workaround for this?
I have been using https://github.com/jacktasia/dumb-jump to quickly jump to definitions.
It's not quite there yet, but they've made a lot of progress in the last few months: https://github.com/sass/libsas...
It's not quite there yet, but they've made a lot of progress in the last few months: https://github.com/sass/libsass/wiki/The-LibSass-Compatibili... https://github.com/sass/libsass/milestones/3.2 http://sass-compatibility.github.io/ It's at the point where I can use node-sass and Ruby Sass interchangeably for our (very large) Sass code base at my company, but we also don't rely very heavily on the newest features. Worth a try, anyway. If node-sass doesn't work for you though, there's also a webpack loader for Ruby Sass: https://github.com/ddelbondio/ruby-sass-loader
Comments (0)
No comments yet. Start the discussion.