You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add fast-components-msft as a new package (#3096)
* initial work to create fast-components-msft
* add styles packages for patterns
* add msft anchor
* add msft button
* add msft badge - outstanding issues
* add msft card
* add msft checkbox
* add msft dialog
* add msft divider
* add msft flipper
* add msft progress - do we want to narrow support to align with guidance?
* add msft radio
* add MSFT radio group
* add msft slider and slider-label
* add msft switch
* add msft tabs - need to ensure alignment of tab panel with tabs
* add msft text area
* add msft text field
* export all components from root
* fix eslint errors
* update imports from fast-components
* add .js extension to anything distributed
* update readme to include install instructions
* update prefix to align with fast
* update package.json description
* update tsconfig
* add dependency for fast-components-styles-msft
* update design system provider to use MSFT design system
* remove js extensions for the time being
* update imports for fast-foundation
* update behavior imports to correct internal path
* update pathing for forcedColors behavior
* fix order of imports
* update system-colors path
* update imports for shared utils added to foundation
* fix design system signature and update to new textarea api with default slot for label
* remove unused behavior and fix color on text field
* update design system values and remove unused vars
* fix text field focus bug
A set of React components which implements the Microsoft styling.
4
+
5
+
## Installation
6
+
7
+
`npm i --save @microsoft/fast-components-msft`
8
+
9
+
### Known issue with Storybook site hot-reloading during development
10
+
11
+
Storybook will watch modules for changes and hot-reload the module when necessary. This is usually great but poses a problem when the module being hot-reloaded defines a custom element. A custom element name can only be defined by the `CustomElementsRegistry` once, so reloading a module that defines a custom element will attempt to re-register the custom element name, throwing an error because the name has already been defined. This error will manifest with the following message:
12
+
`Failed to execute 'define' on 'CustomElementRegistry': the name "my-custom-element-name" has already been used with this registry`
13
+
14
+
This is a known issue and will indicate that you need to refresh the page. We're working on surfacing a more instructive error message for this case.
0 commit comments