Blanket

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.

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.

#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)

#176786, (opens new window) 30a4108a8fe56, (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/blanket, 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).

#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.

#12328, (opens new window) f166f5398b2, (opens new window) - In this version we made Blanket faster and lighter

• General performance improvements

• BREAKING Blanket now accepts a children prop whose value is of type ReactElement.

• BREAKING canClickThrough prop is now renamed to shouldAllowClickThrough.

Running the codemod cli

To run the codemod: You first need to have the latest version installed

Once upgraded, use @atlaskit/codemod-cli:

The CLI will show a list of components and versions so select @atlaskit/blanket@^12.0.0 and you will automatically be upgraded.

What will be changed:

• It will rename the canClickThrough prop to shouldAllowClickThrough.

Run npx @atlaskit/codemod-cli -h for more details on usage.

For Atlassians, refer to the documentation, (opens new window) for more details on the codemod CLI.

#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]6d744d3ff1, (opens new window):

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

Updated dependencies 57c0487a02, (opens new window):

• @atlaskit/button@13.3.11

[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/analytics-next@6.3.5
• @atlaskit/button@13.3.7
• @atlaskit/theme@9.5.1

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

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

Updated dependencies 4a223473c5, (opens new window):

• @atlaskit/theme@9.5.0
• @atlaskit/button@13.3.5

[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]35d2229b2a, (opens new window):

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

[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]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]9f8ab1084b, (opens new window):

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

[patch]bbff8a7d87, (opens new window):

Fixes bug, missing version.json file

[patch]18dfac7332, (opens new window):

In this PR, we are:

• Re-introducing dist build folders
• Adding back cjs
• Replacing es5 by cjs and es2015 by esm
• Creating folders at the root for entry-points
• Removing the generation of the entry-points at the root Please see this ticket, (opens new window) or this page, (opens new window) for further details

[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.

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

Added missing tslib dep

• Updated event type for onBlanketClicked prop

• 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.

• Updated Blanket to TypeScript. Flow types are no longer exported.

• @atlaskit/docs@7.0.3
• @atlaskit/button@12.0.3
• @atlaskit/theme@8.1.7

• @atlaskit/docs@7.0.2
• @atlaskit/analytics-next@4.0.3
• @atlaskit/theme@8.1.6
• @atlaskit/button@12.0.0

• @atlaskit/docs@7.0.1
• @atlaskit/analytics-next@4.0.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.

• @atlaskit/analytics-next@3.1.2
• @atlaskit/button@10.1.1
• @atlaskit/theme@7.0.1
• @atlaskit/docs@6.0.0

• @atlaskit/docs@5.2.3
• @atlaskit/button@10.0.4
• @atlaskit/theme@7.0.0

• @atlaskit/docs@5.2.1
• @atlaskit/analytics-next@3.1.1
• @atlaskit/theme@6.2.1
• @atlaskit/button@10.0.0

• Refine and fix some flow type errors found by fixing @atlaskit/analytics-next HOCs to allow flow to type check properly

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

• @atlaskit/analytics-next@3.0.4
• @atlaskit/button@9.0.5
• @atlaskit/theme@5.1.3

• @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/analytics-next@3.0.1
• @atlaskit/button@9.0.2
• @atlaskit/docs@5.0.1

• @atlaskit/analytics-next@3.0.0
• @atlaskit/button@9.0.0
• @atlaskit/theme@5.0.0
• @atlaskit/docs@5.0.0

• @atlaskit/analytics-next@3.0.0
• @atlaskit/button@9.0.0
• @atlaskit/theme@5.0.0
• @atlaskit/docs@5.0.0

• @atlaskit/theme@4.0.3
• @atlaskit/button@8.1.1
• @atlaskit/docs@4.1.1

• @atlaskit/docs@4.1.0
• @atlaskit/theme@4.0.2
• @atlaskit/button@8.1.0

• @atlaskit/button@8.0.1
• @atlaskit/theme@4.0.1
• @atlaskit/docs@4.0.1

• @atlaskit/button@8.0.0
• @atlaskit/theme@4.0.0
• @atlaskit/docs@4.0.0

• @atlaskit/button@7.2.5
• @atlaskit/theme@3.2.2
• @atlaskit/docs@3.0.4