Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create @uifabric alias packages #15150

Closed
ecraig12345 opened this issue Sep 21, 2020 · 1 comment
Closed

Create @uifabric alias packages #15150

ecraig12345 opened this issue Sep 21, 2020 · 1 comment

Comments

@ecraig12345
Copy link
Member

ecraig12345 commented Sep 21, 2020

As part of the version 8 release, we're renaming our @uifabric packages to the @fluentui scope (see #13384).

For the following packages which are used by the suite, we'll add @uifabric aliases (which re-export the @fluentui version) so that partners who depend on multiple suite versions won't get multiple versions of all the dependency packages.

  • @uifabric/file-type-icons
  • @uifabric/foundation
  • @uifabric/icons
  • @uifabric/merge-styles
  • @uifabric/react-hooks
  • @uifabric/set-version
  • @uifabric/styling
  • @uifabric/utilities

For each of these packages, the alias package will be set up as follows:

  • Located somewhere like /packages/aliases/<pkg-name>
  • Depends on the corresponding @fluentui package and moves in lockstep with it (add beachball config to ensure this)
  • Contains the same top-level files as the real package (re-exporting the real versions)

This should ideally be done pre-beta but could slip to early in the beta period if needed.

@ecraig12345
Copy link
Member Author

Trying to handle package renames and getting rid of major-lockstep at the same time turned out to be too complex, so we will be continuing with major-lockstep for now and NOT making any alias packages. However, we will likely provide a codemod to help with renames (see #15661).

@microsoft microsoft locked as resolved and limited conversation to collaborators Nov 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant