Range

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.

f0bf5f838abd5, (opens new window) - Apply Volt entry-point and barrel-removal standards across these packages. Public exports now resolve directly to ./src/* implementations instead of intermediate ./src/entry-points/* re-exports.

Prefer published subpaths over the package root or internal entry-point paths:

If you imported through 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.

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

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

• The scrubber now applies the same color as the foreground
• The disabled state has been altered; it's now a consistently applied opacity state overlay across the whole element
• The input now uses :focus-visible, rather than :focus and applies an offset focus ring

#18526, (opens new window) 17d9edaa415, (opens new window) - In preparation for compiled adoption, internal styling has been rewritten to remove dynamic styles. This includes custom theming using the theme prop, which has been removed.

If you are not using the theme prop, there should be no breaking changes.

#14777, (opens new window) 21c178539a2, (opens new window) - [ux] Instrumented range with the new theming package, @atlaskit/tokens.

New tokens will be visible only in applications configured to use the new Tokens API (currently in alpha). These changes are intended to be interoperable with the legacy theme implementation. Legacy dark mode users should expect no visual or breaking changes.

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

#2137, (opens new window) da1c8c16d4, (opens new window) - In this version we made range dramatically faster and lighter 🤩

In 4.0.0 we bring significant performance improvements all for just the cost of 1 breaking change 😮. That's not all folks because this update comes with a 🤑 FREE 🤑 codemod for you to upgrade with.

• Range no longer has a peerDependency on styled-components@3. Internally range is now using @emotion/core for styling
• A performance issue made the range noticeably laggy with large ranges. With this change we are no longer creating new classes on each step change and instead updating a css variable, making Range noticeably smoother.
• Changed the inputRef prop to be ref which returns the ref of the range input using React.forwardRef. This new ref prop will accept the type of the old inputRef prop, (input?: HTMLInputElement) => any, as well as if ref is created with React.createRef.
• A new example that shows off how to rate limit your onChange event

• You first need to upgrade to 4.0.0 before you run the codemod cli. This is because the cli will look in your local node_modules for the codemod which is published inside the spinner package.
• The codemod is pretty clever, and will respect aliasing as well as using custom naming for the default import

The codemod will change the inputRef prop to ref

[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/checkbox@10.1.7
• @atlaskit/theme@9.5.1
• @atlaskit/tooltip@15.2.3

[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):

Updated dependencies 6a8bc6f866, (opens new window):

• @atlaskit/theme@9.5.0
• @atlaskit/checkbox@10.1.5
• @atlaskit/tooltip@15.2.1

[patch]557a8e2451, (opens new window):

Rebuilds package to fix typescript typing error.

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

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

• @atlaskit/checkbox@10.0.0
• @atlaskit/docs@8.1.7

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

Type definition files are now referenced in package.json

• @atlaskit/checkbox@9.0.0

[patch]4615439434, (opens new window):

index.ts will now be ignored when publishing to npm

[major]4a08d1912e, (opens new window):

@atlaskit/range 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/tooltip@15.0.0

• @atlaskit/checkbox@8.0.0
• @atlaskit/theme@9.1.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.

• This major release indicates that this package is no longer under dev preview but is ready for use

• onChange is no longer overridden by spread props. As a result this component should now work in uncontrolled mode

• @atlaskit/docs@7.0.3
• @atlaskit/checkbox@6.0.4
• @atlaskit/tooltip@13.0.4
• @atlaskit/theme@8.1.7

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

• Added test to make sure the props are passed down to hidden input

• @atlaskit/checkbox@5.0.9
• @atlaskit/theme@7.0.1
• @atlaskit/tooltip@12.1.13
• @atlaskit/docs@6.0.0

• Change API to experimental theming API to namespace component themes into separate contexts and make theming simpler. Update all dependant components.

• Initial release