openpanel/packages/ably/CHANGELOG.md

@refinedev/ably

4.1.8

Patch Changes

• 6bd14228760d3e1e205ea9248e427f9afa2ec046 Thanks @BatuhanW! - chore: added type qualifier to imports used as type only.

  - import { A } from "./example.ts";
  + import type { A } from "./example.ts";
  

4.1.7

Patch Changes

• #5945 90930b381d8d369c63bc59beedf69c391875166d Thanks @aliemir! - chore: added type qualifier to imports used as type only.

  - import { A } from "./example.ts";
  + import type { A } from "./example.ts";
  

4.1.6

Patch Changes

• #5765 0c197d82393 Thanks @aliemir! - refactor: package bundles and package.json configuration for exports

  Previously, Refine packages had exported ESM and CJS bundles with same .js extension and same types for both with .d.ts extensions. This was causing issues with bundlers and compilers to pick up the wrong files for the wrong environment. Now we're outputting ESM bundles with .mjs extension and CJS bundles with .cjs extension. Also types are now exported with both .d.mts and .d.cts extensions.

  In older versions ESM and CJS outputs of some packages were using wrong imports/requires to dependencies causing errors in some environments. This will be fixed since now we're also enforcing the module type with extensions.

  Above mentioned changes also supported with changes in package.json files of the packages to support the new extensions and types. All Refine packages now include exports fields in their configuration to make sure the correct bundle is picked up by the bundlers and compilers.

• #5754 56ed144a0f5 Thanks @alicanerdurmaz! - chore: TypeScript upgraded to v5.x.x. #5752

4.1.5

Patch Changes

• #5695 79865affa1c Thanks @BatuhanW! - chore: apply biome format and fix lint errors.

4.1.4

Patch Changes

• #5425 190af9fce2 Thanks @aliemir! - Updated @refinedev/core peer dependencies to latest (^4.46.1)

4.1.3

Patch Changes

• #5330 7c8827b43d Thanks @BatuhanW! - chore: upgrade nock library version to ^13.4.0

4.1.2

Patch Changes

• #5022 80513a4e42f Thanks @BatuhanW! - chore: update README.md

  • fix grammar errors.
  • make all README.md files consistent.
  • add code example code snippets.

4.1.1

Patch Changes

• #5022 80513a4e42f Thanks @BatuhanW! - chore: update README.md

  • fix grammar errors.
  • make all README.md files consistent.
  • add code example code snippets.

4.1.0

Minor Changes

• Thanks @aliemir, @alicanerdurmaz, @batuhanW, @salihozdemir, @yildirayunlu, @recepkutuk! Moving to the @refinedev scope 🎉🎉

  Moved to the @refinedev scope and updated our packages to use the new scope. From now on, all packages will be published under the @refinedev scope with their new names.

  Now, we're also removing the refine prefix from all packages. So, the @pankod/refine-core package is now @refinedev/core, @pankod/refine-antd is now @refinedev/antd, and so on.

Patch Changes

3.31.0

Minor Changes

• #3822 0baa99ba787 Thanks @BatuhanW! - - refine v4 release announcement added to "postinstall". - refine v4 is released 🎉 The new version is 100% backward compatible. You can upgrade to v4 with a single command! See the migration guide here: https://refine.dev/docs/migration-guide/3x-to-4x

3.30.0

Minor Changes

• #3822 0baa99ba787 Thanks @BatuhanW! - - refine v4 release announcement added to "postinstall". - refine v4 is released 🎉 The new version is 100% backward compatible. You can upgrade to v4 with a single command! See the migration guide here: https://refine.dev/docs/migration-guide/3x-to-4x

3.29.0

Minor Changes

• Update type declaration generation with tsc instead of tsup for better navigation throughout projects source code.

3.28.0

Minor Changes

• #2440 0150dcd070 Thanks @aliemir! - Update type declaration generation with tsc instead of tsup for better navigation throughout projects source code.

3.27.0

Minor Changes

• All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

3.26.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

3.22.2

Patch Changes

• Updated dependencies [2deb19babf]:
  • @pankod/refine-core@3.23.2