v0.2.2

@pearpages/pulp-tokens 0.2.1

Patch Changes

• a6731f0: Every stylesheet now starts by restating the cascade-layer order (@layer reset, tokens, vendor, base, components, utilities;). Layers rank by first appearance, and a bundler decides which file loads first: when a component stylesheet was linked before the reset, components became the weakest layer and the reset won, so a primary Button painted as bare text. That is what the deployed Storybook was doing. Importing @pearpages/pulp-css first is still the recommended setup, but correct rendering no longer depends on it.

@pearpages/pulp-css 0.1.3

Patch Changes

• a6731f0: Every stylesheet now starts by restating the cascade-layer order (@layer reset, tokens, vendor, base, components, utilities;). Layers rank by first appearance, and a bundler decides which file loads first: when a component stylesheet was linked before the reset, components became the weakest layer and the reset won, so a primary Button painted as bare text. That is what the deployed Storybook was doing. Importing @pearpages/pulp-css first is still the recommended setup, but correct rendering no longer depends on it.
• Updated dependencies [a6731f0]
  • @pearpages/pulp-tokens@0.2.1

@pearpages/pulp-react 0.2.2

Patch Changes

• a6731f0: Every stylesheet now starts by restating the cascade-layer order (@layer reset, tokens, vendor, base, components, utilities;). Layers rank by first appearance, and a bundler decides which file loads first: when a component stylesheet was linked before the reset, components became the weakest layer and the reset won, so a primary Button painted as bare text. That is what the deployed Storybook was doing. Importing @pearpages/pulp-css first is still the recommended setup, but correct rendering no longer depends on it.
• Updated dependencies [a6731f0]
  • @pearpages/pulp-tokens@0.2.1

Docs: https://pulp.pearpages.com · Compare: v0.2.1...v0.2.2