Originally reported in sass/node-sass#1402

foo
  bar

Should produce the following warning

WARNING on line 2 of test.sass:
This selector doesn't have any properties and will not be rendered.

Seems that the current behaviour of Ruby Sass vs libSass/sass2scss is different in regards requiring a space after a colon :.

For example a valid syntax in both:

.very-secret
  display: none

Invalid in Ruby Sass, while libSass via sass2scss accepts:

.very-secret
  display:none

(Originally filed as sass/libsass#2652)

LibSass currently seems to allow semicolons at the end of the line in the indented syntax. This doesn't match the behavior of Ruby Sass or Dart Sass, both of which consider semicolons unknown characters in the indented syntax. Support for semicolons should be deprecated and eventually removed.

Input

/*
some comments
*/

Output

/* */
some comments;
*/;

Which license would be suitable for this project?

http://opensource.org/licenses/

Perhaps MIT?

Once selected, mention it in every file.

While cleaning up my forks, I found this commit https://github.com/paazmaya/sass2scss/commit/56131397ea475db70de0ccb6cab7461c9cd75f00, which might be used to reduce the change for typing error, by using a constant in the places where whitespace is looked for.

The commit also contains using a local variable, instead of calling string position several times. There might be a reason for doing so, but if not, how about using the local variable.

I can make a PR out of that, it useful.

The following

.testing
  :margin
    :bottom 32px
    :foo
      :bar 1px
      :baz 2px
    :baz 3px
  :end 4px

Should result in

.testing {
  margin-bottom: 32px;
  margin-foo-bar: 1px;
  margin-foo-baz: 2px;
  margin-baz: 3px;
  end: 4px; }

To acheive this we definitely need to keep track of the bem partial stack (to unwind it later). Indicators are if line starts with exactly one colon : followed by one identifier.

sass/libsass#1781
sass/node-sass#1300

While building tests for https://github.com/paazmaya/grunt-sass2scss, came across strange behaviour.

The given Sass file:

/**
 * This is third file
*/
@import 'styles-2'

// Imports include the other file

label
  // Use the variable from the other file
  color: $color-white

with sass2scss -c < input.sass > output.scss, the resulted SCSS file:

/*** This is third file */*/ {}@import 'styles-2';/* Imports include the other file */label { /* Use the variable from the other file */color: $color-white; }

Package manager for C++, https://www.biicode.com/

Will be adding whatever is needed for it via PR

Looks like semi-colons are sometimes permitted:

$pink: #ffc3cd
$black: #000

body
  background: $pink;
  color: $black;

While in other situations, they error as expected:

@import "part";
$pink: #ffc3cd;
$black: #000;

Testing through Node-sass v0.9.3, I’d be happy to do a PR here but it looks like most of the testing is through the Perl version, right?

Downstream bug report at sass/libsass#2514

@import foo/bar, baz

Originally reported in sass/node-sass#1402

foo
  bar: baz;

Should produce the following error

Error: Invalid CSS after "baz": expected expression (e.g. 1px, bold), was ";"
        on line 2 of test.sass

Version v1.1.2

See sass/libsass#2637 sass/libsass#2638

input

@import url(http://fonts.googleapis.com/css?family=Limelight&subset=latin,latin-ext)

expected output

@import url(http://fonts.googleapis.com/css?family=Limelight&subset=latin,latin-ext)

actual output

@import url(http://fonts.googleapis.com/css?family=Limelight&subset=latin,"latin-ext)";

Running ./sass2scss -h should provide short list of allowed options and usage example, while ./sass2scss -v should provide version information, based on possible release numbers or the given commit from which the current binary has been build.

Basically a duplicate of sass/libsass#431

Locally tested and the quick fix would seem to be to check that once + is found, it is not followed by (space).

From sass/node-sass#1619

Running 7709939

m.saper.info> /home/saper/sw/sass2scss/sass2scss --version
v1.1.2-7-g7709
m.saper.info> git clone https://github.com/saper/node-sass-issue-1619/
Cloning into 'node-sass-issue-1619'...
remote: Enumerating objects: 7, done.
remote: Counting objects: 100% (7/7), done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 7 (delta 2), reused 7 (delta 2), pack-reused 0
Unpacking objects: 100% (7/7), done.
m.saper.info> cd node-sass-issue-1619/
m.saper.info> git branch
* pure-utf-8
m.saper.info> /home/saper/sw/sass2scss/sass2scss < _config.sass | hd
00000000  24 62 61 63 6b 67 72 6f  75 6e 64 3a 20 62 6c 61  |$background: bla|
00000010  63 6b 3b                                          |ck;|

00000013
m.saper.info> /home/saper/sw/sass2scss/sass2scss < _config.sass | hd
m.saper.info> git checkout utf-8-bom
Branch 'utf-8-bom' set up to track remote branch 'utf-8-bom' from 'origin'.
Switched to a new branch 'utf-8-bom'
m.saper.info> vi _config.scss       
m.saper.info> /home/saper/sw/sass2scss/sass2scss < _config.sass | hd
00000000  ef bb bf 20 7b 7d 24 62  61 63 6b 67 72 6f 75 6e  |... {}$backgroun|
00000010  64 3a 20 62 6c 61 63 6b  3b                       |d: black;|
00000019

BOM should be banned, but maybe this should be somehow handled. In the end libsass complains:

m.saper.info> /home/saper/sw/libsass/sassc/bin/sassc -v
sassc: 3.6.1
libsass: 3.6.2
sass2scss: 1.1.1
sass: 3.5
m.saper.info> /home/saper/sw/sass2scss/sass2scss < _config.sass | /home/saper/sw/libsass/sassc/bin/sassc 
Error: Invalid CSS after "": expected 1 selector or at-rule, was "{}$background: blac"
        on line 1:1 of stdin
>>  {}$background: black;
   ^

Would these recent changes be worth of making a feature release?
v1.1.2...master

Perhaps due to recent changes, or not, but currently the following Sass:

@font-face
  font-family: 'Inder'
  font-style: normal
  font-weight: normal
  src: url('http://fonts/inder.eot?#iefix') format('embedded-opentype')

becomes SCSS:

@font-face {
  font-family: 'Inder';
  font-style: normal;
  font-weight: normal;
  src: url('http:; }//fonts/inder.eot?#iefix') format('embedded-opentype')

Without the // part seems to work as one would expect, valid SCSS.

Perhaps for the comment check, there should be added exclusion if the // is immediately after with :?

From sass/libsass#1990: If ":host" should be a selector, use "\:host" instead.

I have verified that \:host should indeed be converted to :host {}.

.a
  +
    .c, .b
      margin: 10px

Ruby Sass

.a + .c, .a + .b {
  margin: 10px; }

LibSass 3.3.7

Error: Invalid CSS after "  @include": expected identifier, was "{"
        on line 2 of test.sass
>>   @include  {

Hi, I was directed here from sass/node-sass#1719 (comment)

Since upgrading to [email protected], which I think meant also upgrading to [email protected], I have been getting the following error:

Error: property "checked" must be followed by a ':'

with the following code:

div
  :checked ~ p
    display: none

I can fix this with:

div
  input:checked ~ p
    display: none

However, the first syntax is valid and should work (I think!). I don't know if this bug was introduced by f03b821 but it seems related. Let me know if I can help with any further info. Thanks!

Would it be possible to start tagging releases as this project now seems to work on a rather huge piles of Sass?

Hey just wanted to check if there was a way to generate a sourcemap for the compiled SCSS file from sass2scss? I was interested in using your library to make a SASS linter on top of https://github.com/causes/scss-lint, and a sourcemap would definitely make it easier to do.

https://github.com/mgreter/sass2scss/blob/master/sass2scss.cpp#L176

size_t pos_value = sass.find_first_of(" \t\n\v\f\r", pos_left);

returns 18446744073709551615 (which is string::npos) and seems to be the cause for sass/libsass#410

The given sass string contains ::selection and has a length of 11 characters. pos_left is 0.

Perhaps there should be added a check against string::npos to skip the given step?