Closed Bug 1366868 Opened 8 years ago Closed 6 years ago

Add PostCSS to asset pipeline

Categories

(developer.mozilla.org Graveyard :: General, enhancement)

Product:
developer.mozilla.org Graveyard
Component:
General
Platform:
All
Other
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jwhitlock, Unassigned)

References

Details

(Keywords: in-triage, Whiteboard: [specification][type:feature])

What problem would this feature solve? ====================================== PostCSS is a popular [1] tool that uses JavaScript plugins to process CSS. These plugins would allow reusing community supported plugins for: - Adjusting font size - Setting vendor prefixes - Adding RGBA fallbacks - Combining duplicates (such as RTL and media queries) into single declarations [1] https://twitter.com/PostCSS/status/689886395763179522 Who has this problem? ===================== Staff contributors to MDN How do you know that the users identified above have this problem? ================================================================== Our front-end developers (on MDN and mozilla.org) read about PostCSS being used to solve issues, and want to use it. How are the users identified above solving this problem now? ============================================================ We're using sass mixins, under Kuma config management, to provide some of these features. Do you have any suggestions for solving the problem? Please explain in detail. ============================================================================== - Add PostCSS to the Docker and gulp environments - Continue to process .sass files to .css with libsass - Run PostCSS on the resulting .css files - Migrate functionality from sass mixins to PostCSS plugins Is there anything else we should know? ======================================
I started this work, but encountered several issues with the static pipeline that made it difficult, and that I'd like to fix first. Added blocking tracking bug 1380419
Depends on: 1380419
Closing PR https://github.com/mozilla/kuma/pull/4244 , which had the attempt to hack in PostCSS
Blocks: 1486527

During our last dev bug triage meeting this item came up again. With our current work of switching to React, rearchitecting the front-end code-base and switching from Django pipeline to Webpack, there is a lot of changes that will take place with regards to JavaScript, CSS, SASS etc.

This coupled with other work related to our key results for the year, puts us in a position where we simply cannot evaluate the feasibility of additional tools. I do see the benefit of PostCSS, but for now, we need to focus on the other items mentioned here.

The upside of these changes will be that, in future, evaluating new tools such as PostCSS as part of our toolchain will be much, much simpler. Thank you for your suggestion Exe-Boss.

I am going to close this as Won't fix for the moment, but we can surely reevaluate this once the dust has settled ;)

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.