Migration Guide

From 2.x to 3.x

1. Update dependencies:

npm install bulma-social@^3 bulma@^1

2. Keep your CSS imports as-is (css/all.min.css and css/single/* paths are still valid in v3).
3. If you want hover transitions, add .is-animated to each button. In v3 transitions are opt-in.

<!-- Before (2.x: transitions enabled by default) -->
<a class="button is-facebook">
  <span>Continue with Facebook</span>
</a>

<!-- After (3.x: add .is-animated to enable transitions) -->
<a class="button is-facebook is-animated">
  <span>Continue with Facebook</span>
</a>

4. If you import internal Sass files, update single-provider paths to: sass/social-providers/single/

// Before
@use "bulma-social/sass/social-providers/facebook";

// After
@use "bulma-social/sass/social-providers/single/facebook";

5. Remove any usage of combineSocialProviders(). Provider colors are now centralized in sass/utilities/_providers.scss and generated via the utilities pipeline.

From 1.x to 2.x (and then to 3.x)

1. Update your main CSS import path:

before: bin/bulma-social.min.css
after:  css/all.min.css

2. Confirm your project uses Bulma >= 1.0.0.
3. Continue with the 2.x → 3.x checklist above.

Verification Checklist

• Your app builds without Sass import errors.
• Buttons render with expected provider colors.
• Transitions are enabled only where .is-animated is present.
• No references remain to removed helper APIs.