less / less/less-plugin-clean-css
1.6.0 ignores cli arguments
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 193
- Forks
- 41
- Avg merge
- 7h 43m
- Merged PRs (30d)
- 2
Description
When command line arguments are provided, they no longer have any impact on the outcome.
Given file.less:
/*! hello */
/*! world */
foo { bar: 1 }
and compiled using:
lessc file.less --clean-css="--s1 --advanced --compatibility=ie8" file.css
Expected outcome:
/*! hello */foo{bar:1}
Actual outcome:
/*! hello *//*! world */foo{bar:1}
Context
package.json:
{
"dependencies": {
"less": "^4.2.0",
"less-plugin-clean-css": "^1.6.0"
}
}
clean-css: 5.3.3
less-plugin-clean-css: 1.6.0
less: 4.2.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the lessc command and the versions listed in package.json, then trace how the plugin receives and forwards the --clean-css arguments. Done means the supplied options affect compression so the output retains only one /*! comment, matching the expected CSS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100