Open Bug 1583311 Opened 3 years ago Updated 2 months ago

[META] choose & impl updated CSS strategy for New Tab in m-c

Categories

(Firefox :: Messaging System, task)

task

Tracking

()

People

(Reporter: dmosedale, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Keywords: meta)

Currently, New Tab is using node-sass as a way to move faster and keep style sheets more maintainable. These sources are built into CSS files, and these artifacts are built with the (binary) node-sass npm package and then checked into m-c. In order to make uplifts cleaner and easier, we need to do any CSS transpiling as part of the normal m-c build process. There are several options:

  • Vendor in node-sass, and hook it up to the m-c build process. We would need to convince ourselves that the binary, license and security implications of vendoring in node-sass are worth it, which might be complicated.
  • Switch to vanilla CSS.
  • Choose a minimal alternative solution, likely using and vendoring in PostCSS. CSS modules is one possibility.
Blocks: ujmc
Depends on: 1459771
Depends on: 1459690
No longer depends on: 1459690
No longer blocks: bugzy-epic
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.