Fix Storybook compilation in components package

[aduth]

Related to #103103

Proposed Changes

• Fixes Storybook compilation in @automattic/components package by ensuring that Calypso's Webpack-based Storybook compilation is able to match the calypso:src exports, using conditionNames (similar to what we do in the main client compilation).

Why are these changes being made?

• So that Storybook previews can compile successfully

Testing Instructions

Verify both Storybook build produces no errors:

yarn workspace @automattic/components run storybook:build

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-432e1ee3218b734f0f6af99b8c4f2febc0df395f

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-432e1ee3218b734f0f6af99b8c4f2febc0df395f&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-432e1ee3218b734f0f6af99b8c4f2febc0df395f&env=a8c-for-agencies

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• help-center
• notifications

To test WordPress.com changes, run install-plugin.sh $pluginSlug fix/storybook-styles-export on your sandbox.

[matticbot]

This PR does not affect the size of JS and CSS bundles shipped to the user's browser.

Generated by performance advisor bot at iscalypsofastyet.com.

[jsnajdr]

Looks good 👍 The /styles/* path exports only define the calypso:src condition, so a webpack compilation must have it in conditionNames.

[aduth]

Looks good 👍 The /styles/* path exports only define the calypso:src condition, so a webpack compilation must have it in conditionNames.

On that note, should it be that we only export the styles on the calypso:src condition? Would this potentially cause downstream issues for consumers which need access to those paths? I think it can make sense to be conservative about which entrypoints we expose, but for a components package in particular we'd need some way to expose styles.

[jsnajdr]

On that note, should it be that we only export the styles on the calypso:src condition?

When I was adding the additional (non-root) exports I was primarily fixing Calypso compilation errors, and for that the calypso:src field was sufficient. And now it's up to debate for each of the additional exports whether we want to keep it indefinitely, or whether it was a temporary patch that should be removed.

The @automattic/components/styles/* export is used for exactly one thing: the wp-button-override.scss style that @mirka added in #101626. And this PR's description considers this style temporary:

While we may want to abstract this differently in the near future, having this override class available will unblock us quickly for now in a way that's relatively simple to refactor.