Autoprefix cause extra source "<input css 1>" in source map file
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- tooling
Research direction
Reproduce the report with the shown JavaScript snippet, enabling source maps and the autoprefix plugin. Trace how the generated source map records its sources; done means the unwanted "<input css 1>" source is no longer included.
Written by the indexing model from the issue text.
Description
This is my code:
var option = {
paths: [ '/data/src/less/' ],
plugins: [autoprefixPlugin],
sourceMap: true
};
less.render(data, option).then( (output) => {
//My code
});
- Dominant language
- JavaScript
- Stars
- 169
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from less/less-plugin-autoprefix
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
less/less-plugin-autoprefix#42 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
less/less-plugin-autoprefix#37 · 2 comments ·
-
Enable grid layoutsOpen
Difficulty 3/5 1-2 days Newbie friendliness 45/100
less/less-plugin-autoprefix#36 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
less/less-plugin-autoprefix#31 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
All issues in less/less-plugin-autoprefix
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 25 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libnativeapi/nativeapi#21 ·
-
area: core complexity: easy impact: medium
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
ueberdosis/tiptap#8668 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day