@fluentui/react-portal-compat-context 9.0.3 → 9.0.4

package/CHANGELOG.json

@@ -2,7 +2,28 @@
   "name": "@fluentui/react-portal-compat-context",
   "entries": [
     {
-      "date": "Thu, 20 Oct 2022 08:35:17 GMT",
+      "date": "Fri, 11 Nov 2022 14:53:19 GMT",
+      "tag": "@fluentui/react-portal-compat-context_v9.0.4",
+      "version": "9.0.4",
+      "comments": {
+        "patch": [
+          {
+            "author": "tristan.watanabe@gmail.com",
+            "package": "@fluentui/react-portal-compat-context",
+            "commit": "792bd72b19e360afe9ac8e9da298dc3d85776c74",
+            "comment": "chore: Migrate to new package structure."
+          },
+          {
+            "author": "martinhochel@microsoft.com",
+            "package": "@fluentui/react-portal-compat-context",
+            "commit": "b3907043bd8d7b650c55e8e7c3119b14f2606c38",
+            "comment": "fix: create valid export maps"
+          }
+        ]
+      }
+    },
+    {
+      "date": "Thu, 20 Oct 2022 08:39:41 GMT",
       "tag": "@fluentui/react-portal-compat-context_v9.0.3",
       "version": "9.0.3",
       "comments": {

package/CHANGELOG.md

@@ -1,12 +1,22 @@
 # Change Log - @fluentui/react-portal-compat-context
 
-This log was last generated on Thu, 20 Oct 2022 08:35:17 GMT and should not be manually modified.
+This log was last generated on Fri, 11 Nov 2022 14:53:19 GMT and should not be manually modified.
 
 <!-- Start content -->
 
+## [9.0.4](https://github.com/microsoft/fluentui/tree/@fluentui/react-portal-compat-context_v9.0.4)
+
+Fri, 11 Nov 2022 14:53:19 GMT 
+[Compare changes](https://github.com/microsoft/fluentui/compare/@fluentui/react-portal-compat-context_v9.0.3..@fluentui/react-portal-compat-context_v9.0.4)
+
+### Patches
+
+- chore: Migrate to new package structure. ([PR #25481](https://github.com/microsoft/fluentui/pull/25481) by tristan.watanabe@gmail.com)
+- fix: create valid export maps ([PR #25558](https://github.com/microsoft/fluentui/pull/25558) by martinhochel@microsoft.com)
+
 ## [9.0.3](https://github.com/microsoft/fluentui/tree/@fluentui/react-portal-compat-context_v9.0.3)
 
-Thu, 20 Oct 2022 08:35:17 GMT 
+Thu, 20 Oct 2022 08:39:41 GMT 
 [Compare changes](https://github.com/microsoft/fluentui/compare/@fluentui/react-portal-compat-context_v9.0.2..@fluentui/react-portal-compat-context_v9.0.3)
 
 ### Patches

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@fluentui/react-portal-compat-context",
-  "version": "9.0.3",
+  "version": "9.0.4",
   "description": "A package that holds React context for compatibility of React Contexts",
   "main": "lib-commonjs/index.js",
   "module": "lib/index.js",
-  "typings": "dist/index.d.ts",
+  "typings": "./dist/index.d.ts",
   "sideEffects": false,
   "repository": {
     "type": "git",
@@ -38,5 +38,13 @@
       "major",
       "prerelease"
     ]
+  },
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./lib/index.js",
+      "require": "./lib-commonjs/index.js"
+    },
+    "./package.json": "./package.json"
   }
 }

package/Spec.md

@@ -1,63 +0,0 @@
-# @fluentui/react-portal-compat-context Spec
-
-## Background
-
-_Description and use cases of this component_
-
-## Prior Art
-
-_Include background research done for this component_
-
-- _Link to Open UI research_
-- _Link to comparison of v7 and v0_
-- _Link to GitHub epic issue for the converged component_
-
-## Sample Code
-
-_Provide some representative example code that uses the proposed API for the component_
-
-## Variants
-
-_Describe visual or functional variants of this control, if applicable. For example, a slider could have a 2D variant._
-
-## API
-
-_List the **Props** and **Slots** proposed for the component. Ideally this would just be a link to the component's `.types.ts` file_
-
-## Structure
-
-- _**Public**_
-- _**Internal**_
-- _**DOM** - how the component will be rendered as HTML elements_
-
-## Migration
-
-_Describe what will need to be done to upgrade from the existing implementations:_
-
-- _Migration from v8_
-- _Migration from v0_
-
-## Behaviors
-
-_Explain how the component will behave in use, including:_
-
-- _Component States_
-- _Interaction_
-  - _Keyboard_
-  - _Cursor_
-  - _Touch_
-  - _Screen readers_
-
-## Accessibility
-
-Base accessibility information is included in the design document. After the spec is filled and review, outcomes from it need to be communicated to design and incorporated in the design document.
-
-- Decide whether to use **native element** or folow **ARIA** and provide reasons
-- Identify the **[ARIA](https://www.w3.org/TR/wai-aria-practices-1.2/) pattern** and, if the component is listed there, follow its specification as possible.
-- Identify accessibility **variants**, the `role` ([ARIA roles](https://www.w3.org/TR/wai-aria-1.1/#role_definitions)) of the component, its `slots` and `aria-*` props.
-- Describe the **keyboard navigation**: Tab Oder and Arrow Key Navigation. Describe any other keyboard **shortcuts** used
-- Specify texts for **state change announcements** - [ARIA live regions
-  ](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions) (number of available items in dropdown, error messages, confirmations, ...)
-- Identify UI parts that appear on **hover or focus** and specify keyboard and screen reader interaction with them
-- List cases when **focus** needs to be **trapped** in sections of the UI (for dialogs and popups or for hierarchical navigation)
-- List cases when **focus** needs to be **moved programatically** (if parts of the UI are appearing/disappearing or other cases)