Why variable to cannot be used as a range parameter? about postcss-for

[xori]

@for @i from 1 to $max-columns {
  .col-t-@i { width: calc(@i / $max-columns * 100%); }
}

IMO I think you could get away with making it a variable that simple-var doesn't recognize. I also think that it would make semantic sense as the variable @i is specific to this code block.

Now you can run this after simple-vars but before calc and you're golden.

Update:
for anyone who happens upon this with google like I did, I forked this repo to enable the above syntax. I just needed it to just-work™
@antyakushev maybe you'd consider a modified pull request to allow both the $i syntax or the @i syntax

[antyakushev]

@xori I assumed that postcss-custom-properties, which is css future syntax, can be used for this.
For now I'll mention both of the ways in the ReadMe to make googling easier.

[antyakushev]

That's how PostCSS works. Postcss-for cannot be used after postcss-simple-vars since it will replace loop's $i. And being put before, postcss-for won't know the value variable stands for.

[antyakushev]

Have any ideas on solving this, without ruining postcss's modularity?

[tunnckoCore]

since it will replace loop's $i

that's the idea, but hmm..
you have right, maybe it make more sense for foreach loop for collections.