-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Renaming @fluentui/react to @fluentui/react-northstar #12302
Conversation
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: 69fe48c5b3f2d64004ede907c5e6eb3e0d1c31e8 (build) |
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Perf comparison
Perf tests with no regressions
|
…c-react into fluent-ui-exp # Conflicts: # packages/fluentui/react-experimental/src/themes/teams-high-contrast/componentStyles.ts # packages/fluentui/react-experimental/src/themes/teams-high-contrast/components/Menu/menuItemStyles.ts
…c-react into fluent-ui-exp
@miroslavstastny I believe we are ready to go here; can you help with merge/publish/update teams? I will start on the oufr aliasing pr next. |
🎉 Handy links: |
Setting out to address these goals for customers:
Know which component package to use when (@fluentui/react@7 vs office-ui-fabric-react vs@fluentui/react@0 is confusing. Instead we will have
@fluentui/react
,@fluentui/react-next
, and@fluentui/react-northstar
.)Ensure that the current production LTS channel can live side by side with "next" and "northstar" code.
To meet these needs, we will be renaming the
@fluentui/react
package to@fluentui/react-northstar
.BREAKING CHANGE
This means that
@fluentui/react
package imports would be changed to@fluentui/react-northstar
. It is possible however to use new versions of the packages without changing imports via npm aliasing:Microsoft Reviewers: Open in CodeFlow