---
# System prepended metadata

title: What to do about package versioning and naming part 342357320948

---

# What to do about package versioning and naming part 342357320948

## Concerns with renaming @uifabric to @fluentui scopes

### Deep imports could break

```jsx=
import { css } from '@uifabric/utilities/lib/css';
```

How will this continue to work?

* Option A: fork library; @uifabric version stays in 7.0 branch, @fluentui version goes into master and is major bumped (possibly?)
  * Upside: Does not break deep imports
  * Upside: Code lives in predictable place
  * Downside: Duplicate code in bundle
* Option B: Alias package just export * from '@fluentui/utilities' and break deep imports. 7.0 branch does not contain code
  * Upside: No duplicate code
  * Upside: No duplicate code
  * Downside: Breaks deep imports


## Conclusion
- rename fluentui to uifabric scope
- no alias packages
- major bump (lock-step) sub-packages for this version 
  - Will probably try and get rid of major lockstep in v9 when we're not also doing so many renames/moves
- all v7 packages stay in 7.0 branch
- If we have time later this week, should try and write down learnings from the versioning/branching/package branch location strategies we considered or started on but didn't go through with (since we might use them later)
