microsoft / microsoft/monaco-editor
[Bug] Autoprefixer warns about end value in CSS when building with Next.js.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46.8k
- Forks
- 4.1k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 1
Description
Reproducible in vscode.dev or in VS Code Desktop?
- Not reproducible in vscode.dev or VS Code Desktop
Reproducible in the monaco editor playground?
- Not reproducible in the monaco editor playground
Monaco Editor Playground Link
autoprefixer: end value has mixed support, consider using flex-end instead
(Triggered by: node_modules/monaco-editor/esm/vs/editor/contrib/hover/browser/hover.css)
Monaco Editor Playground Code
Reproduction Steps
No response
Actual (Problematic) Behavior
No response
Expected Behavior
No response
Additional Context
No response
Contributor guide
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 with the reported Autoprefixer warning and the referenced node_modules/monaco-editor/esm/vs/editor/contrib/hover/browser/hover.css path. Reproduce the build with Next.js, then trace which Monaco Editor stylesheet produces the warning; done means the build no longer reports this warning without changing unrelated behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, next.js
- Domain
- build-system, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100