Release

[derTobsch]

Hey @matthew-dean,

thanks for merging #37. Is there anything I can do/help to get a release of the main branch? If there is anything I can do please let me know.

[matthew-dean]

@derTobsch Sorry, I've been extremely busy with my full-time job this year. Do you have experience publishing to NPM? I wonder if I can grant permissions to just publish for this package. If so, what is your NPM username?

[RichardHabeeb]

Bumping this, the package is 9 years old on npmjs. I'd be happy to update it (user name richardhabeeb), but it might be easier for you to update the version number and run npm publish yourself.

[derTobsch]

How would it be if we setup a GitHub action to release this package? Therefore there should be no further challanges to release early and often. How do you release less?

[matthew-dean]

@derTobsch Both are manual publish processes right now.

[matthew-dean]

@derTobsch @RichardHabeeb Published 1.6.0. Can you check that it looks good?

[peterdstone]

@import "path/to/my/stylsheet.css";

at the top of our less file is bing stripped out since the latest build

before and according to the spec these would have been left as is

[peterdstone]

as in I have a less file of the structure below:

@import "path/to/my/stylsheet.css";

///other stuff here

if I runn lessc over it I get:

@import "path/to/my/stylsheet.css";

///other stuff here

but if I run lessc with the --clean-css I get:

///other stuff here

if I change the import to:

@import (inline) "path/to/my/stylsheet.css";

the the css is pulled in and inlined, but that's not what I want