A React Framework for building internal tools, admin panels, dashboards & B2B apps with unmatched flexibility.
MIT License
Bot releases are visible (Hide)
Published by refine-bot 6 months ago
#5886 f3ddcce0bf5
Thanks @abdelrahman-essawy! - fix: add ability to customize default permission without explicitly passing them on each mutation
fixing an issue which didn't allow users to override the default readPermissions
/ writePermissions
values Role.any()
, by passing defaultReadPermissions
/ defaultWritePermissions
OR by passing meta?.readPermissions
/ meta?.writePermissions
.
ba719f6ea26
Thanks @aliemir! - fix: declaration files in node10, node16 and nodenext module resolutionsPublished by refine-bot 6 months ago
#5868 a82ef6afc15
Thanks @Ac-Srikanth! - feat: add message prop for required auth input fields for the above packages.
Now you can provide custom required messages with translate feature for all auth input fields(Login, register, forget password,update password).
Resolves #5855
#5887 113c1337bf0
Thanks @aliemir! - chore: remove version lock from @ant-design/icons 5.0.1 to ^5.0.1
#5920 df0dad6ca46
Thanks @aliemir! - fix: lock antd
version to 5.16.5
due to broken builds in 5.17.0
In the latest release of antd
package, Next.js apps are failing to build or taking extremely long time to build. Until this issue is fixed in the antd
package, we are locking the version to 5.16.5
to prevent any build issues.
Related issue antd/#48758
#5881 ba719f6ea26
Thanks @aliemir! - fix: declaration files in node10, node16 and nodenext module resolutions
Updated dependencies [ba719f6ea26
]:
Published by refine-bot 6 months ago
ba719f6ea26
Thanks @aliemir! - fix: declaration files in node10, node16 and nodenext module resolutionsPublished by refine-bot 7 months ago
#5823 aedc6a2961c
Thanks @aliemir! - fix: broken lodash imports in ESM builds
Fixed lodash imports in ESM builds which requires lodash-es
imports to use .js
extension to work properly unless the bundler is configured to handle non-fully-specified imports.
Resolves #5822
Published by refine-bot 7 months ago
#5823 aedc6a2961c
Thanks @aliemir! - fix: broken lodash imports in ESM builds
Fixed lodash imports in ESM builds which requires lodash-es
imports to use .js
extension to work properly unless the bundler is configured to handle non-fully-specified imports.
Resolves #5822
Updated dependencies [aedc6a2961c
]:
Published by refine-bot 7 months ago
#5823 aedc6a2961c
Thanks @aliemir! - fix: broken lodash imports in ESM builds
Fixed lodash imports in ESM builds which requires lodash-es
imports to use .js
extension to work properly unless the bundler is configured to handle non-fully-specified imports.
Resolves #5822
Updated dependencies [aedc6a2961c
]:
Published by refine-bot 7 months ago
aedc6a2961c
]:
Published by refine-bot 7 months ago
#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
Updated dependencies [4e8188a6652
, 10ba9c34490
, 2b5ac6f5409
, 0c197d82393
, 0c197d82393
, 404b2ef5e1b
, 56ed144a0f5
, 0c197d82393
, 10ba9c34490
, 38f129f40ee
, f32512b9042
]:
Published by refine-bot 7 months ago
#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
#5808 10ba9c34490
Thanks @aliemir! - chore: updated refresh button tests to be more UI focused and hand off the logic to the @refinedev/core
's useRefreshButton
hook
#5755 404b2ef5e1b
Thanks @BatuhanW! - fix: incorrect type imports
Updated dependencies [4e8188a6652
, 10ba9c34490
, 2b5ac6f5409
, 0c197d82393
, 0c197d82393
, 404b2ef5e1b
, 56ed144a0f5
, 0c197d82393
, 10ba9c34490
, 38f129f40ee
, f32512b9042
]:
Published by refine-bot 7 months ago
#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
Published by refine-bot 7 months ago
#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
Published by refine-bot 7 months ago
#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
Published by refine-bot 7 months ago
#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
Published by refine-bot 7 months ago
#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
Published by refine-bot 7 months ago
#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
#5755 404b2ef5e1b
Thanks @BatuhanW! - fix: incorrect type imports
Published by refine-bot 7 months ago
#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
Published by refine-bot 7 months ago
#5754 56ed144a0f5
Thanks @alicanerdurmaz! - chore: TypeScript upgraded to v5.x.x. #5752
fixed: Some type errors are fixed due to the TypeScript upgrade.
#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.
#5765 0c197d82393
Thanks @aliemir! - Fixed the lodash-es
imports for ESM builds to access the exports properly.
#5714 38f129f40ee
Thanks @aliemir! - Due to the bug fix made in the @refinedev/core
, onFinishAutoSave
's returned promise can now reject and should be handled accordingly. Updated useForm
's auto save handler to catch the rejection without breaking the application.
Additionally due to the same changes, onFinish
should also be handled accordingly. Updated useForm
's saveButtonProps.onClick
to catch the rejection without breaking the application.
#5755 404b2ef5e1b
Thanks @BatuhanW! - fix: incorrect type imports
Published by refine-bot 7 months ago
#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
Published by refine-bot 7 months ago
#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
Published by refine-bot 7 months ago
#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.
#5765 0c197d82393
Thanks @aliemir! - Fixed the lodash-es
imports for ESM builds to access the exports properly.
#5754 56ed144a0f5
Thanks @alicanerdurmaz! - chore: TypeScript upgraded to v5.x.x. #5752