parcel-bundler / parcel-bundler/lightningcss
@nest does not print warning as indicated
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.7k
- Forks
- 302
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
According to the doc, using @nest should print a warning. However, it does not seem to be the case unless I am misleading.
My command:
lightningcss --nesting --custom-media --targets 'safari 14.1 or chrome 100 or firefox 90' css/theme.css -o dist/assets/theme.css --bundle
LightningCSS bundle the file without any warning in the console.
Is there some special flag to enable to show warnings?
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 by reproducing the reported lightningcss --nesting --custom-media --targets 'safari 14.1 or chrome 100 or firefox 90' ... --bundle command and compare its output with the documentation's @nest warning behavior. Trace the warning path from the CLI entry point; done means the documented warning is emitted or the documentation clearly explains the required flag and actual behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100