682: Whiskey, Security, Antitrust, and Fun with CSS Functions

What It Covers

Chris and Dave explore CSS custom functions and if statements, discuss npm security vulnerabilities affecting chalk and strip-ansi packages, analyze Google's antitrust case resolution allowing Chrome retention, and debate authentication challenges for children.

Key Questions Answered

• •CSS @function syntax: Chrome 139 introduces custom CSS functions using @function with dash-dash naming, result property for return values, and source-order-based precedence where lowest declaration wins, enabling logic abstraction from declarative styles into reusable functions with media query support.
• •npm security response: Storybook reduced dependencies working with E18E efficiency group, avoiding the two-hour window when chalk and strip-ansi were compromised through phishing attack. Projects with fewer base-level dependencies face lower risk when supply chain attacks target widely-used terminal formatting libraries.
• •Google antitrust outcome: Judge Mehta ruled Google can retain Chrome and continue paying Apple for default search placement, requiring only search index data sharing with competitors and syndication services availability. Forcing Chrome sale would create downstream harms affecting browser investment and web platform development funding.
• •CSS if function pattern: The if function consolidates multiple result statements into condition-value pairs separated by semicolons, supporting media and supports queries. This switch-statement-like syntax improves readability when handling ten-plus breakpoints compared to stacked @media blocks with repeated result declarations.