Tooltip

d82e6f76528ab, (opens new window) - Add direct subpath package exports as part of the linking-platform, search, media, and design-system barrel-removal (de-barrel) migration.

These packages now expose their individual modules via explicit package.json exports subpaths so that consumers can import directly from the leaf module (e.g. @atlaskit/pkg/thing) instead of the package barrel/index. This adds new public entry points without changing or removing any existing exports, so it is a backwards-compatible additive change.

No runtime behaviour changes; this is an API-surface (entry-point) addition to support tree-shaking and to unblock removal of the barrel index files.

6902b31db1608, (opens new window) - Consolidate direct Popper.js callers behind @atlaskit/popper compatibility entry points and feature-gated consumer adapters.

@atlaskit/popper now exposes compatibility entry points so existing direct popper.js / react-popper callers can move their dependency ownership onto @atlaskit/popper without a full rewrite:

• @atlaskit/popper/react-popper re-exports the React usePopper hook and Manager / Popper / Reference render-prop components.
• @atlaskit/popper/unsafe-imperative re-exports the raw Popper.js v2 createPopper for non-React, imperative callers. This is an escape hatch for existing callers only. Do not use it for new code; build new overlays on @atlaskit/top-layer instead.

Updated dependencies

c9014b843f7ea, (opens new window) - Apply Volt entry-point and multi-export standards via volt-migrate-package. This is a major change to @atlaskit/tooltip: the package exports map has been restructured so every public subpath now resolves directly to its ./src/* implementation instead of going through an intermediate ./src/entry-points/* re-export. No public subpaths were removed.

Because each subpath now points straight at its implementation module, a subpath and the package root can resolve to the same module instance. Consumers that deep-import the internal entry-points/* files, or that jest.mock() a specific subpath, may observe changed resolution/behaviour and need updating. For example, this package's /Tooltip mock must handle render-prop function children (see the accompanying Confluence blog-tree test fix).

Importing the published subpaths (or the package root) continues to work as before:

If you were reaching into the internal entry-point modules, switch to the public subpath:

cd097a2111788, (opens new window) - Republish packages depending on @atlaskit/react-compiler-gating so their published dependency reference is updated to the renamed @atlaskit/react-compiler-gating scope.

The earlier rename of @atlassian/react-compiler-gating to @atlaskit/react-compiler-gating only bumped the renamed package itself, so dependent packages were never republished and their published versions still referenced the old @atlassian/react-compiler-gating name, which is not available in the public npm registry. This minor bump republishes all affected packages with the corrected dependency.

f2dc9097319f0, (opens new window) - ### Dropped support for legacy Typescript 4 types. Typescript 5 is now the new minimum.

Removes the typesVersions property and dist/types-ts4.5 directory from the dist.

Types are now exclusively via the "types": "dist/types/index.d.ts" property.

cf4af9aa9a2fe, (opens new window) - Fix tooltip with position="mouse-x" / position="mouse-y" not respecting the mousePosition prop when the platform-dst-top-layer feature flag is enabled.

The cursor-anchored tooltip is now positioned via a new useAnchorPositionAtPoint hook in @atlaskit/top-layer, which delegates to useAnchorPosition against a hidden anchor element placed once at the cursor location at show time. The popover stays anchored at that location and does not follow subsequent pointer movement.

useAnchorPosition now also accepts an optional isEnabled prop (defaults to true); when false, the hook is a no-op.

• Dialog registers as type: 'modal', with a no-op onClose, as there is no current use case for programmatic close of modals via the open layer observer.
• Popover registers as type: 'popup' for interactive overlay roles (dialog, alertdialog, menu, listbox, tree, grid) and omits type for other roles (e.g. tooltip).
• A new programmatic value has been added to TPopoverCloseReason to distinguish programmatic closes, such as those from the open layer observer's closeLayers() calls.

7250582895c0b, (opens new window) - Top-layer adoption work behind the platform-dst-top-layer feature flag. Public adopter APIs are intentionally kept narrow while the top-layer API surface settles, with one exception called out below.

Highlights:

• Pass the full [along, away] legacy popper offset through to the new top-layer placement.offset API (via fromLegacyPlacement). Previously only the away axis was forwarded, which dropped the along offset for consumers of Popup, PopupSelect, Spotlight, and Tooltip when platform-dst-top-layer is enabled.
• Fix broken import of dialogHeight and dialogWidth from the removed utils module in @atlaskit/modal-dialog.

Public API:

• @atlaskit/tooltip (minor): add an optional testId?: string field to TriggerProps. This is additive (no existing prop changes shape). Required because @atlaskit/button/new (and other Pressable-backed primitives) overwrite data-testid from spread, so the legacy (triggerProps as any)['data-testid'] workaround is silently absorbed by those consumers. A typed testId field flows through their own testId destructure instead, restoring data-testid propagation onto the rendered trigger element.
• @atlaskit/popup, @atlaskit/dropdown-menu (patch): no public type changes. Wider aria-haspopup unions that the FF-on path produces are bridged at the package boundary into @atlaskit/top-layer with localised FUDGE(top-layer-api) casts, documented in packages/design-system/top-layer/notes/decisions/migration-roadmap.md ("Open API decisions deferred to a follow-up PR"). They will be widened in a follow-up minor PR once the top-layer API is committed.
• @atlaskit/modal-dialog, @atlaskit/select, @atlaskit/spotlight (patch/minor): no public type changes; bug fixes only.

Merge-readiness fixes (FF-on test wiring + adopter behavior):

• @atlaskit/popup (minor): wire the compositional PopupContent to delegate to PopupContentTopLayer when platform-dst-top-layer is enabled. Previously only the legacy Popup component had the FF branch, leaving consumers of the compositional API on the legacy popper path.
• @atlaskit/select (minor): add an onClick handler to the PopupSelect top-layer trigger so clicks open/close the menu (mirrors the legacy global click handler in popup-select.tsx). Add explicit Escape handling on the menu's onKeyDown so the menu closes and focus returns to the trigger.
• @atlaskit/top-layer (patch): the <dialog> rendered by the Dialog primitive now sets aria-modal="true" explicitly. Modern browsers infer modal semantics from .showModal() but some assistive tech still keys off the explicit attribute.
• @atlaskit/top-layer (patch): guard use-anchor-positioning against environments where ResizeObserver is not defined (e.g. jest's node environment, used by the post-office test suite). The observer is used to wait for the popover's first valid layout before measuring; consumers in non-DOM jest environments now get a no-op observer and the scroll/resize listeners still apply if the host environment polyfills showPopover. Real browsers always have ResizeObserver.
• @atlaskit/modal-dialog (patch): on the FF-on path, drop the tabIndex={-1} (and unused :focus-visible outline) from the modal content wrapper. The native <dialog>.showModal() focus-delegate algorithm picks the first focusable descendant (including tabindex=-1), and the wrapper was hijacking initial focus from the close button. Also honor shouldReturnFocus={ref} on the FF-on path (an unmount-cleanup focuses the ref after dialog.close() so it overrides the browser's automatic return-to-trigger). Boolean shouldReturnFocus={false} is not yet honored on the FF-on path — see top-layer/notes/merge-blockers.md.
• @atlaskit/datetime-picker (patch): on the FF-on path, set mode="manual" on the Popup.Content rendered by both internal/menu-top-layer.tsx (date-picker calendar) and internal/fixed-layer-menu-top-layer.tsx (time-picker menu). With the default mode="auto", the same click event that opens the menu (which targets the react-select combobox input — outside the popover element) bubbles to the browser's native popover light-dismiss handler and immediately closes the menu. react-select / DateTimePicker already own outside-click and Esc dismissal via their own state, so opting out of the native auto-dismiss is the correct integration. Also extend the existing Esc → trigger-focus restoration in components/date-picker.tsx to the FF-on path (manual mode disables the browser's built-in focus return, and the legacy code path was already handling this for itself behind an FF negation).
• @atlaskit/popup (no public API change): no source changes — only FF-on Playwright spec/example fixes drove the suite from 21/3/2 to 27/0/0. Notable: the two test.fixme'd nested-popover cases were not browser limitations; popover="auto" chains correctly via DOM ancestry (the original fixmes had the wrong testId selector). Added testId props to two examples (16-popup-with-a11y-props, 18-should-fit-container) so default-shape tests can reach the trigger.
• Test alignment for FF-on Playwright suites across popup, select, datetime-picker, inline-dialog, inline-message, and modal-dialog: selector updates to match the new top-layer testId convention (${testId}--content, [role="dialog"][aria-label="calendar"]), per-spec skipAxeCheck() for example-level color-contrast violations unrelated to the migration, and focus assertions adjusted to match native <dialog> / Popup.Content auto-focus semantics (focus lands on the first focusable child, not the dialog container itself).
• @atlassian/capacity-planning-capacity-graph, @atlaskit/color-picker, @atlassian/timeline-table, @atlassian/global-side-navigation (patch): scope fg mocks in unit tests so platform-dst-top-layer returns false. JSDOM does not implement the native Popover API (showPopover/hidePopover/toggle events), so leaving the gate ON in unit tests caused popover content to remain in the DOM after close and broke close-behaviour assertions. Browser coverage for the FF-on path is provided by the Playwright suites listed above.
• @atlaskit/dropdown-menu (no public API change): test/example-only fixes for the FF-on Playwright suite. Added role="menuitem" to the nested-trigger ButtonItem in examples/93-testing-nested-keyboard-navigation-top-layer.tsx to satisfy axe's aria-required-children rule on the parent menu. Added a test.beforeEach(skipAxeCheck) to dropdown-menu.spec.tsx (FF-on suite) for example-level color-contrast violations on the pre-existing color.text.selected/color.background.selected token pair (3.91:1). Replaced a deadlocking await expect(moveItem).not.toBeFocused() pre-open assertion (Playwright's auto-wait blocks 5s on the absent element) with await expect(moveItem).not.toBeVisible(). Suite result: 22/22 passing.

2bed6255731de, (opens new window) - Top-layer adoption work behind the platform-dst-top-layer feature flag. Public adopter APIs are intentionally kept narrow while the top-layer API surface settles, with one exception called out below.

Highlights:

• Pass the full [along, away] legacy popper offset through to the new top-layer placement.offset API (via fromLegacyPlacement). Previously only the away axis was forwarded, which dropped the along offset for consumers of Popup, PopupSelect, Spotlight, and Tooltip when platform-dst-top-layer is enabled.
• Fix broken import of dialogHeight and dialogWidth from the removed utils module in @atlaskit/modal-dialog.

Public API:

• @atlaskit/tooltip (minor): add an optional testId?: string field to TriggerProps. This is additive (no existing prop changes shape). Required because @atlaskit/button/new (and other Pressable-backed primitives) overwrite data-testid from spread, so the legacy (triggerProps as any)['data-testid'] workaround is silently absorbed by those consumers. A typed testId field flows through their own testId destructure instead, restoring data-testid propagation onto the rendered trigger element.
• @atlaskit/popup, @atlaskit/dropdown-menu (patch): no public type changes. Wider aria-haspopup unions that the FF-on path produces are bridged at the package boundary into @atlaskit/top-layer with localised FUDGE(top-layer-api) casts, documented in packages/design-system/top-layer/notes/decisions/migration-roadmap.md ("Open API decisions deferred to a follow-up PR"). They will be widened in a follow-up minor PR once the top-layer API is committed.
• @atlaskit/modal-dialog, @atlaskit/select, @atlaskit/spotlight (patch/minor): no public type changes; bug fixes only.

Merge-readiness fixes (FF-on test wiring + adopter behavior):

• @atlaskit/popup (minor): wire the compositional PopupContent to delegate to PopupContentTopLayer when platform-dst-top-layer is enabled. Previously only the legacy Popup component had the FF branch, leaving consumers of the compositional API on the legacy popper path.
• @atlaskit/select (minor): add an onClick handler to the PopupSelect top-layer trigger so clicks open/close the menu (mirrors the legacy global click handler in popup-select.tsx). Add explicit Escape handling on the menu's onKeyDown so the menu closes and focus returns to the trigger.
• @atlaskit/top-layer (patch): the <dialog> rendered by the Dialog primitive now sets aria-modal="true" explicitly. Modern browsers infer modal semantics from .showModal() but some assistive tech still keys off the explicit attribute.
• @atlaskit/top-layer (patch): guard use-anchor-positioning against environments where ResizeObserver is not defined (e.g. jest's node environment, used by the post-office test suite). The observer is used to wait for the popover's first valid layout before measuring; consumers in non-DOM jest environments now get a no-op observer and the scroll/resize listeners still apply if the host environment polyfills showPopover. Real browsers always have ResizeObserver.
• @atlaskit/modal-dialog (patch): on the FF-on path, drop the tabIndex={-1} (and unused :focus-visible outline) from the modal content wrapper. The native <dialog>.showModal() focus-delegate algorithm picks the first focusable descendant (including tabindex=-1), and the wrapper was hijacking initial focus from the close button. Also honor shouldReturnFocus={ref} on the FF-on path (an unmount-cleanup focuses the ref after dialog.close() so it overrides the browser's automatic return-to-trigger). Boolean shouldReturnFocus={false} is not yet honored on the FF-on path — see top-layer/notes/merge-blockers.md.
• @atlaskit/datetime-picker (patch): on the FF-on path, set mode="manual" on the Popup.Content rendered by both internal/menu-top-layer.tsx (date-picker calendar) and internal/fixed-layer-menu-top-layer.tsx (time-picker menu). With the default mode="auto", the same click event that opens the menu (which targets the react-select combobox input — outside the popover element) bubbles to the browser's native popover light-dismiss handler and immediately closes the menu. react-select / DateTimePicker already own outside-click and Esc dismissal via their own state, so opting out of the native auto-dismiss is the correct integration. Also extend the existing Esc → trigger-focus restoration in components/date-picker.tsx to the FF-on path (manual mode disables the browser's built-in focus return, and the legacy code path was already handling this for itself behind an FF negation).
• @atlaskit/popup (no public API change): no source changes — only FF-on Playwright spec/example fixes drove the suite from 21/3/2 to 27/0/0. Notable: the two test.fixme'd nested-popover cases were not browser limitations; popover="auto" chains correctly via DOM ancestry (the original fixmes had the wrong testId selector). Added testId props to two examples (16-popup-with-a11y-props, 18-should-fit-container) so default-shape tests can reach the trigger.
• Test alignment for FF-on Playwright suites across popup, select, datetime-picker, inline-dialog, inline-message, and modal-dialog: selector updates to match the new top-layer testId convention (${testId}--content, [role="dialog"][aria-label="calendar"]), per-spec skipAxeCheck() for example-level color-contrast violations unrelated to the migration, and focus assertions adjusted to match native <dialog> / Popup.Content auto-focus semantics (focus lands on the first focusable child, not the dialog container itself).
• @atlassian/capacity-planning-capacity-graph, @atlaskit/color-picker, @atlassian/timeline-table, @atlassian/global-side-navigation (patch): scope fg mocks in unit tests so platform-dst-top-layer returns false. JSDOM does not implement the native Popover API (showPopover/hidePopover/toggle events), so leaving the gate ON in unit tests caused popover content to remain in the DOM after close and broke close-behaviour assertions. Browser coverage for the FF-on path is provided by the Playwright suites listed above.
• @atlaskit/dropdown-menu (no public API change): test/example-only fixes for the FF-on Playwright suite. Added role="menuitem" to the nested-trigger ButtonItem in examples/93-testing-nested-keyboard-navigation-top-layer.tsx to satisfy axe's aria-required-children rule on the parent menu. Added a test.beforeEach(skipAxeCheck) to dropdown-menu.spec.tsx (FF-on suite) for example-level color-contrast violations on the pre-existing color.text.selected/color.background.selected token pair (3.91:1). Replaced a deadlocking await expect(moveItem).not.toBeFocused() pre-open assertion (Playwright's auto-wait blocks 5s on the absent element) with await expect(moveItem).not.toBeVisible(). Suite result: 22/22 passing.

• Renames UNSAFE_shouldRenderToParent to shouldRenderToParent
• Renames UNSAFE_shouldAlwaysFadeIn to shouldAlwaysFadeIn

38f89455de21d, (opens new window) - Removes tooltip/utilities entrypoint from public API. Use the utility exports from @atlaskit/tooltip directly.

Removes redundant utility files, split-out multi-export modules and restructures internal files.

d26b520fd7859, (opens new window) - The keyboard shortcut font has been updated to use regular fonts instead of monospace fonts, for improved readability and distinction between characters such as the letter O and number 0. It will now use the font.body.small font token.

This change was previously behind the feature gate platform-tooltip-shortcuts-regular-font, which has now been removed.

e273fa0610764, (opens new window) - The keyboard shortcut font has been updated to use regular fonts instead of monospace fonts, for improved readability and distinction between characters such as the letter O and number 0. It will now use the font.body.small font token.

This change is behind the feature gate platform-tooltip-shortcuts-regular-font.

8f79c1a030071, (opens new window) - The built-in support for displaying keyboard shortcuts via the shortcut prop is now available for use. It was previously behind the platform-dst-tooltip-shortcuts feature flag, which has now been cleaned up.

The top and bottom padding of the tooltip container has also been increased from 2px to 4px - this change previously also behind the same feature flag.

6915142a30a40, (opens new window) - The tooltip keyboard shortcut component has been updated to protect against global styles in apps, by unsetting styles. Minor tweaks to the keyboard shortcut styling have also been made - font size, height, and center alignment.

The shortcut prop is still behind the feature flag platform-dst-tooltip-shortcuts.

4afb88f83d688, (opens new window) - Tooltip now includes support for displaying keyboard shortcuts via the shortcut prop. This prop is currently behind the platform-dst-tooltip-shortcuts feature flag. Example usage:

#117363, (opens new window) 10a0f7f6c2027, (opens new window) - This package's peerDependencies have been adjusted for react and/or react-dom to reflect the status of only supporting React 18 going forward. No explicit breaking change to React support has been made in this release, but this is to signify going forward, breaking changes for React 16 or React 17 may come via non-major semver releases.

Please refer this community post for more details: https://community.developer.atlassian.com/t/rfc-78-dropping-support-for-react-16-and-rendering-in-a-react-18-concurrent-root-in-jira-and-confluence/87026, (opens new window)

#174355, (opens new window) d0d1aae2aa428, (opens new window) - Migrated from @emotion/react to @compiled/react in order to improve performance, align with the rest of the Atlaskit techstack, and support React 18 Streaming SSR. Please note, in order to use this version of @atlaskit/tooltip, you will need to ensure that your bundler is configured to handle .css imports correctly.

Most bundlers come with built-in support for .css imports, so you may not need to do anything. If you are using a different bundler, please refer to the documentation for that bundler to understand how to handle .css imports. For more information on the migration, please refer to RFC-73 Migrating our components to Compiled CSS-in-JS, (opens new window).

• Added new prop: isScreenReaderAnnouncementDisabled which can be used to disable hidden text for tooltips. This is useful when the Tooltip content matches the Tooltip trigger content as hidden text is not required.

#127511, (opens new window) db30e29344013, (opens new window) - Widening range of react and react-dom peer dependencies from ^16.8.0 || ^17.0.0 || ~18.2.0 to the wider range of ``^16.8.0 || ^17.0.0 || ^18.0.0` (where applicable).

This change has been done to enable usage of react@18.3 as well as to have a consistent peer dependency range for react and react-dom for /platform packages.

#22642, (opens new window) 45ebe7af434, (opens new window) - Moved to using declarative entrypoints internally. Public API is unchanged.

4efc76f8a72, (opens new window) - [ux] Fixes a bug where tooltip entrance and exit direction animations were not working since version 12.1.7, after upgrading react-popper.

This involved adding a wrapper <div> around the tooltip to separate the positioning and animation styles. The wrapper can be identified in tests using testId with the pattern {testId}--wrapper.

Updated dependencies

#9083, (opens new window) 8386261266c, (opens new window) - Tooltip content now supports an optional render props API. This API provides an update function which can be called to manually recalculate the position of the tooltip.

This update function is useful if you are changing the content of the tooltip while it is being displayed.

#5693, (opens new window) d36905cfe9, (opens new window) - Fixed incorrect function signature for onShow and onHide props, and added improved typing for these props.

• old: analyticsEvent was the first argument
• change: analyticsEvent became the second argument unintentionally (bug introduced 17.0.0)
• now: restoring old behavior, analyticsEvent as the first argument

If you migrated analyticsEvent to the second argument to mitigate this bug, you will need to update your code.

Updated dependencies

#4424, (opens new window) 83586f015e, (opens new window) - Tooltip has been refactored to improve performance and be compliant with the lite-mode specification.

• Removed react-transition-group in favor of @atlaskit/motion to reduce bundle size
• Removed react-node-resolver because of its use of React.findDOMNode which has been marked as deprecated by the React team (more below...)
• Removes analytics-next HOCs in favor of hook variant (You may need to update snapshot tests)
• Removes all usage of HOCs
• Replaces styled-components v3 with @emotion/core to improve runtime and bundle-size
• If you are passing component to the tag prop then your component will need to expose a ref prop (ref: React.Ref<HTMLElement>).

Important to note:

Only a single element can be supplied to Tooltip as children, no plain text etc. (this has not changed from previous version).

• Added official support for nested tooltips within tooltips
• Test IDs will now be applied to the container element as well as the tooltip, with '--container' appended to the end

#3885, (opens new window) 6c525a8229, (opens new window) - Upgraded to TypeScript 3.9.6 and tslib to 2.0.0

Since tslib is a dependency for all our packages we recommend that products also follow this tslib upgrade to prevent duplicates of tslib being bundled.

[patch]3940bd71f1, (opens new window):

Change imports to comply with Atlassian conventions- Updated dependencies cf8577f5d6, (opens new window):

Updated dependencies 6b8e60827e, (opens new window):

Updated dependencies 449ef134b3, (opens new window):

Updated dependencies 57c0487a02, (opens new window):

Updated dependencies fd41d77c29, (opens new window):

• @atlaskit/popper@3.1.12
• @atlaskit/button@13.3.11
• @atlaskit/icon@20.1.1
• @atlaskit/webdriver-runner@0.3.4

• @atlaskit/docs@8.4.0
• @atlaskit/icon@20.1.0
• @atlaskit/webdriver-runner@0.3.0
• @atlaskit/button@13.3.9

• @atlaskit/webdriver-runner@0.2.0
• @atlaskit/button@13.3.8

[patch]6548261c9a, (opens new window):

Remove namespace imports from React, ReactDom, and PropTypes- Updated dependencies 6548261c9a, (opens new window):

• @atlaskit/docs@8.3.2
• @atlaskit/visual-regression@0.1.9
• @atlaskit/analytics-next@6.3.5
• @atlaskit/button@13.3.7
• @atlaskit/icon@20.0.1
• @atlaskit/popper@3.1.11
• @atlaskit/portal@3.1.6
• @atlaskit/theme@9.5.1

• @atlaskit/icon@20.0.0
• @atlaskit/docs@8.3.1
• @atlaskit/button@13.3.6
• @atlaskit/portal@3.1.5

[patch]4a223473c5, (opens new window):

Removes babel/runtime from dependencies. Users should see a smaller bundlesize as a result- Updated dependencies 28f8f0e089, (opens new window):

Updated dependencies 82747f2922, (opens new window):

Updated dependencies 4a223473c5, (opens new window):

• @atlaskit/icon@19.1.0
• @atlaskit/theme@9.5.0
• @atlaskit/button@13.3.5
• @atlaskit/popper@3.1.9
• @atlaskit/portal@3.1.4

[minor]24865cfaff, (opens new window):

Tooltip will now be shown when the target element receives focus and hidden when the target element loses focus.

[patch]24865cfaff, (opens new window):

Updates react-popper dependency to a safe version.- Updated dependencies 24865cfaff, (opens new window):

Updated dependencies 24865cfaff, (opens new window):

Updated dependencies 24865cfaff, (opens new window):

• @atlaskit/analytics-next@6.3.3
• @atlaskit/popper@3.1.8

[patch]d222c2b987, (opens new window):

Theme has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided.

** getTokens props changes ** When defining the value function passed into a ThemeProvider, the getTokens parameter cannot be called without props; if no props are provided an empty object {} must be passed in:

becomes:

** Color palette changes ** Color palettes have been moved into their own file. Users will need to update imports from this:

to this:

or for multi entry-point users:

to this:

[patch]f86839ca4e, (opens new window):

@atlaskit/portal had an issue in IE11 and this is fixed in 3.1.2

[patch]35d2229b2a, (opens new window):

Adding missing license to packages and update to Copyright 2019 Atlassian Pty Ltd.

[minor]ca1d742875, (opens new window):

Adding an optional prop testId that will set the attribute value data-testid. It will help products to write better integration and end to end tests.

[patch]a2d0043716, (opens new window):

Updated version of analytics-next to fix potential incompatibilities with TS 3.6

[patch]097b696613, (opens new window):

Components now depend on TS 3.6 internally, in order to fix an issue with TS resolving non-relative imports as relative imports

[patch]ecca4d1dbb, (opens new window):

Upgraded Typescript to 3.3.x

[patch]708028db86, (opens new window):

Change all the imports to theme in Core to use multi entry points

[patch]b8e9a6c5a3, (opens new window):

Children has now been added to Tooltip's prop-types

[patch]de35ce8c67, (opens new window):

Updates component maintainers

[patch]926b43142b, (opens new window):

Analytics-next has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided. No behavioural changes.

Breaking changes

• withAnalyticsForSumTypeProps alias has been removed, please use withAnalyticsEvents
• AnalyticsContextWrappedComp alias has been removed, please use withAnalyticsContext

Breaking changes to TypeScript annotations

• withAnalyticsEvents now infers proptypes automatically, consumers no longer need to provide props as a generic type.
• withAnalyticsContext now infers proptypes automatically, consumers no longer need to provide props as a generic type.
• Type WithAnalyticsEventProps has been renamed to WithAnalyticsEventsProps to match source code
• Type CreateUIAnalyticsEventSignature has been renamed to CreateUIAnalyticsEvent to match source code
• Type UIAnalyticsEventHandlerSignature has been renamed to UIAnalyticsEventHandler to match source code
• Type AnalyticsEventsPayload has been renamed to AnalyticsEventPayload
• Type ObjectType has been removed, please use Record<string, any> or [key: string]: any
• Type UIAnalyticsEventInterface has been removed, please use UIAnalyticsEvent
• Type AnalyticsEventInterface has been removed, please use AnalyticsEvent
• Type CreateAndFireEventFunction removed and should now be inferred by TypeScript
• Type AnalyticsEventUpdater removed and should now be inferred by TypeScript

[patch]688f2957ca, (opens new window):

Fixes various TypeScript errors which were previously failing silently

[patch]f34776be97, (opens new window):

Type definition files are now referenced in package.json

• @atlaskit/popper@3.0.0

[patch]9f8ab1084b, (opens new window):

Consume analytics-next ts type definitions as an ambient declaration.

[patch]d0db01b410, (opens new window):

TypeScript users of withAnalyticsEvents and withAnalyticsContext are now required to provide props as a generic type. This is so that TypeScript can correctly calculate the props and defaultProps of the returned component.

Before:

After:

[patch]29a1f158c1, (opens new window):

Use default react import in typescript files.

• @atlaskit/docs@8.1.3
• @atlaskit/button@13.0.9
• @atlaskit/portal@3.0.7
• @atlaskit/icon@19.0.0

[patch]93bcf314c6, (opens new window):

Added missing tslib dep

• @atlaskit/tooltip has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided. No API or behavioural changes.

• @atlaskit/docs@8.1.2
• @atlaskit/button@13.0.8
• @atlaskit/portal@3.0.3
• @atlaskit/icon@18.0.0

• This is just a safety release in case anything strange happened in in the previous one. See Pull Request #5942 for details

• @atlaskit/portal@3.0.0

• Updates react and react-dom peer dependencies to react@^16.8.0 and react-dom@^16.8.0. To use this package, please ensure you use at least this version of react and react-dom.

• @atlaskit/portal@1.0.0
• @atlaskit/popper@1.0.0

• @atlaskit/docs@7.0.3
• @atlaskit/button@12.0.3
• @atlaskit/icon@16.0.9
• @atlaskit/popper@0.4.3
• @atlaskit/theme@8.1.7

• @atlaskit/docs@7.0.2
• @atlaskit/analytics-next@4.0.3
• @atlaskit/icon@16.0.8
• @atlaskit/popper@0.4.2
• @atlaskit/portal@0.3.1
• @atlaskit/theme@8.1.6
• @atlaskit/button@12.0.0

• @atlaskit/portal@0.3.0

• @atlaskit/docs@7.0.1
• @atlaskit/analytics-next@4.0.1
• @atlaskit/icon@16.0.5
• @atlaskit/popper@0.4.1
• @atlaskit/portal@0.2.1
• @atlaskit/theme@8.0.1
• @atlaskit/button@11.0.0

[major]76299208e6, (opens new window):

• Drop ES5 from all the flow modules

As a breaking change, all @atlaskit packages will be dropping cjs distributions and will only distribute esm. This means all distributed code will be transpiled, but will still contain import and export declarations.

The major reason for doing this is to allow us to support multiple entry points in packages, e.g:

Previously this was sort of possible for consumers by doing something like:

This has a couple of issues. 1, it treats the file system as API making internal refactors harder, we have to worry about how consumers might be using things that aren't actually supposed to be used. 2. We are unable to do this internally in @atlaskit packages. This leads to lots of packages bundling all of theme, just to use a single color, especially in situations where tree shaking fails.

To support being able to use multiple entrypoints internally, we unfortunately cannot have multiple distributions as they would need to have very different imports from of their own internal dependencies.

ES Modules are widely supported by all modern bundlers and can be worked around in node environments.

We may choose to revisit this solution in the future if we find any unintended condequences, but we see this as a pretty sane path forward which should lead to some major bundle size decreases, saner API's and simpler package architecture.

Please reach out to #fabric-build (if in Atlassian) or create an issue in Design System Support, (opens new window) (for external) if you have any questions or queries about this.

• Move tooltip to render popper in portal to maintain ref that Popper needs to initially position the tooltip

• @atlaskit/portal@0.1.0

• @atlaskit/docs@6.0.1
• @atlaskit/button@10.1.2
• @atlaskit/portal@0.0.18
• @atlaskit/icon@16.0.0

• Remove scroll listener in componentWillMount in Tooltip to fix potential memory leak from 'close' tooltip not properly unmounting when hiding Examples modal via the X button

• @atlaskit/analytics-next@3.1.2
• @atlaskit/button@10.1.1
• @atlaskit/icon@15.0.2
• @atlaskit/popper@0.3.6
• @atlaskit/portal@0.0.17
• @atlaskit/theme@7.0.1
• @atlaskit/docs@6.0.0

• @atlaskit/docs@5.2.3
• @atlaskit/button@10.0.4
• @atlaskit/icon@15.0.1
• @atlaskit/popper@0.3.3
• @atlaskit/theme@7.0.0

• @atlaskit/docs@5.2.2
• @atlaskit/button@10.0.1
• @atlaskit/portal@0.0.16
• @atlaskit/icon@15.0.0

• @atlaskit/docs@5.2.1
• @atlaskit/analytics-next@3.1.1
• @atlaskit/icon@14.6.1
• @atlaskit/popper@0.3.2
• @atlaskit/portal@0.0.15
• @atlaskit/theme@6.2.1
• @atlaskit/button@10.0.0

• @atlaskit/portal@0.0.14

• @atlaskit/portal@0.0.13

• Use @atlaskit/popper internally instead of a custom approach to position management

[patch]7f1ff28, (opens new window):

Fixes error when Tooltip attempts to setState on an unmounted component

• @atlaskit/portal@0.0.12

• @atlaskit/docs@5.0.8
• @atlaskit/button@9.0.13
• @atlaskit/portal@0.0.10
• @atlaskit/icon@14.0.0

• @atlaskit/icon@13.8.1
• @atlaskit/portal@0.0.9

• @atlaskit/portal@0.0.8

• @atlaskit/theme@6.0.0
• @atlaskit/icon@13.2.5
• @atlaskit/button@9.0.6
• @atlaskit/docs@5.0.6

• @atlaskit/portal@0.0.6

• @atlaskit/portal@0.0.6

• @atlaskit/portal@0.0.6

• @atlaskit/portal@0.0.6

• @atlaskit/portal@0.0.5

• @atlaskit/analytics-next@3.0.4
• @atlaskit/button@9.0.5
• @atlaskit/theme@5.1.3
• @atlaskit/portal@0.0.4
• @atlaskit/icon@13.2.4

• @atlaskit/portal@0.0.3
• @atlaskit/icon@13.2.2
• @atlaskit/button@9.0.4
• @atlaskit/theme@5.1.2
• @atlaskit/analytics-next@3.0.3
• @atlaskit/docs@5.0.2

• @atlaskit/analytics-next@3.0.2
• @atlaskit/button@9.0.3
• @atlaskit/theme@5.1.1
• @atlaskit/layer-manager@5.0.3
• @atlaskit/icon@13.2.1

• @atlaskit/analytics-next@3.0.1
• @atlaskit/button@9.0.2
• @atlaskit/docs@5.0.1

• @atlaskit/layer-manager@5.0.1
• @atlaskit/icon@13.1.1

• @atlaskit/analytics-next@3.0.0
• @atlaskit/button@9.0.0
• @atlaskit/theme@5.0.0
• @atlaskit/docs@5.0.0
• @atlaskit/layer-manager@5.0.0
• @atlaskit/icon@13.0.0

• @atlaskit/analytics-next@3.0.0
• @atlaskit/button@9.0.0
• @atlaskit/theme@5.0.0
• @atlaskit/docs@5.0.0
• @atlaskit/layer-manager@5.0.0
• @atlaskit/icon@13.0.0

• @atlaskit/button@8.2.2
• @atlaskit/icon@12.3.1

• @atlaskit/button@8.2.0
• @atlaskit/icon@12.2.0

• @atlaskit/button@8.1.2
• @atlaskit/theme@4.0.4
• @atlaskit/layer-manager@4.2.1
• @atlaskit/icon@12.1.2

• @atlaskit/layer-manager@4.1.0
• @atlaskit/icon@12.1.0
• @atlaskit/docs@4.1.0
• @atlaskit/theme@4.0.2
• @atlaskit/button@8.1.0

• @atlaskit/layer-manager@4.0.1
• @atlaskit/icon@12.0.1
• @atlaskit/button@8.0.1
• @atlaskit/theme@4.0.1
• @atlaskit/docs@4.0.1

• @atlaskit/layer-manager@4.0.0
• @atlaskit/icon@12.0.0
• @atlaskit/button@8.0.0
• @atlaskit/theme@4.0.0
• @atlaskit/docs@4.0.0

• @atlaskit/icon@11.3.0
• @atlaskit/layer-manager@3.0.4
• @atlaskit/button@7.2.5
• @atlaskit/theme@3.2.2
• @atlaskit/docs@3.0.4