PostCSS?

Open
#74 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
css

Research direction

The issue mentions svelte-preprocess and several PostCSS plugins but names no repository files, tests, or entry points. Start by locating the existing style-preprocessing configuration and reviewing how svelte-preprocess is integrated; the work is done only when a specific PostCSS integration and its intended plugin scope are defined and validated.

Written by the indexing model from the issue text.

Description

enhancement

Might be good to add PostCSS for svelte-preprocess. Some possible benefits:

  1. Autoprefixer for vendor prefixes
  2. CSSnext to use new CSS syntax instead of SASS
  3. PreCSS can replace any remaining need for SASS
  4. StyleLint could help with consistency
  5. CSSNano for minification and optimization in production
  6. Font Magician might help with typography stack
Dominant language
Svelte
Stars
6
Forks
9
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wharfkit/web-renderer

All issues in wharfkit/web-renderer

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.