-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Broken NPM Publishes
Tristan Watanabe edited this page May 2, 2023
·
1 revision
In the event that we publish a package version that's broken, follow the steps below to mediate:
- Deprecate the broken version for each package that were recently published and affected.
- Update
latest
tag to point to the last known good version published. You may need to do this not just for the direct package affected but for the whole dependency tree of that package (i.e.fluentui/react
v8 publishes a broken version, all its v8 dependencies and the v8 dependencies of its dependencies and so on) due to caret dependencies.
- FAQ - Fabric and Stardust to Fluent UI
-
@fluentui/react
Version 9 -
@fluentui/react
Version 8 - Contributing to the
7.0
branch - How to apply themes (version 7/8)
- Planning and development process (for work by the core team)
- Conducting meetings Style guide
- Keeping up with review requests
- RFC review process
- Setup (configuring your environment)
- Fluent UI React version 7/8
- CLA
- Overview
- Repo structure
- Development process
- Contributing to previous versions
- API Extractor
- Build command changes made in early 2020
- Component implementation guide
- Creating a component
- Implementation Best Practices
- Theming
- Documenting
- Styling (old approach)
- Overview
- Testing with Jest
- E2E testing (Cypress)
- Visual testing (Screener)
- Accessibility review checklist