@refinedev/mui@5.14.6
Patch Changes
-
#5737
4e8188a6652
Thanks @aliemir! - chore: updated content ofREADME.md
to include installation, usage and scaffolding instructions. -
#5765
0c197d82393
Thanks @aliemir! - fix:dayjs
imports in ESM bundlesdayjs imports in ESM bundles were not being correctly resolved, this has been fixed by adding an esbuild plugin to replace the imports with the correct path for ESM bundles.
-
#5765
0c197d82393
Thanks @aliemir! - Fixed thelodash-es
imports for ESM builds to access the exports properly. -
#5765
0c197d82393
Thanks @aliemir! - refactor: package bundles and package.json configuration for exportsPreviously, 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 includeexports
fields in their configuration to make sure the correct bundle is picked up by the bundlers and compilers.In context of
@refinedev/mui
these changes may cause unexpected issues due to misconfigured bundlers/compilers in some environments.In projects using
react-scripts
, you may have issues with import statements in the@refinedev/mui
's ESM bundle, this should be resolved by customizing the webpack configuration of the project by allowing imports without fully specifying the extensions.An example configuration with
@craco/craco
is as follows:// craco.config.js module.exports = { webpack: { configure: { module: { rules: [ { test: /.m?js$/, resolve: { fullySpecified: false, }, }, ], }, }, }, };
In Remix projects using
@refinedev/mui
you may encounter issues due to ESM issues from Material UI packages, please refer to this issue if you have any problems related to this: mui/material-ui#39765If the error is related with
@refinedev/mui
specifically, settingserverModuleFormat
to"cjs"
will help getting rid of the related errors. -
#5754
56ed144a0f5
Thanks @alicanerdurmaz! - chore: TypeScript upgraded to v5.x.x. #5752 -
#5765
0c197d82393
Thanks @aliemir! - fix: broken eslint plugin for removing test ids from componentsEslint plugin to remove test ids from components was broken and might miss some test ids to be included in the bundles.
-
#5765
0c197d82393
Thanks @aliemir! - fix:@mui/icons-material
imports from ESM builds.@mui/icons-material
imports from ESM builds were not being correctly resolved, this has been fixed by adding an esbuild plugin to replace the imports with the correct path for ESM bundles. -
#5808
10ba9c34490
Thanks @aliemir! - refactor: moved internal logic of buttons to respective hooks from@refinedev/core
We've moved the internal logic of buttons to their respective hooks in the
@refinedev/core
package to ensure consistency and reduce duplication. This change will make it easier to manage and maintain the buttons across different UI integrations of Refine. This will also benefit the users who want to customize the buttons viaswizzle
option or create their own buttons withouth having to duplicate the logic. -
Updated dependencies [
56ed144a0f5
,0c197d82393
,0c197d82393
,56ed144a0f5
,38f129f40ee
,404b2ef5e1b
]:- @refinedev/react-hook-form@4.8.16
- @refinedev/ui-types@1.22.5