less / less/less-plugin-autoprefix
Browser usage is not supported at this time
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 169
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
My current situation does need this functionality. The LESS files are compiled on the client, and we use modifyVars after a settings is changed by the user.
Do you hava an idea how this library could theortically be extended for this to work? I would be willing to contribute.
As less.modifyVars does not return the result, but adapts the DOM, it is not easy to chain an autoprefix after it. A solution could be to look at the latest introduced <style> tag and autoprefix it. Howver that feels really hacky.
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
Start by reviewing the browser-side LESS compilation flow and how modifyVars adapts the DOM. The issue suggests examining the latest injected <style> tag, but names no repository files or tests. Done would mean defining and implementing a supported browser-use extension with a clear way to verify autoprefixing after settings change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100