Releases: dilanx/craco
Releases · dilanx/craco
v7.1.0
What's Changed
- Fix the github link in the docs on the top right by @scottarver in #465
- fix signature for whenXX functions by @liao02x in #468
- Update webpack.md by @TerrySansom in #479
- Fix: proper return type by @galbitz in #482
- Use Jest 27.x types by @levrik in #464
- allow build script to use existing NODE_ENV value by @Maikel-Nait in #480
- feat: Override CRA paths by @attilapolakovics in #489
- update plugins by @ponjs in #492
- docs: add plugin craco-css-modules by @crazyurus in #494
- Fix broken link, fixing typos by @deining in #496
New Contributors
- @scottarver made their first contribution in #465
- @liao02x made their first contribution in #468
- @TerrySansom made their first contribution in #479
- @galbitz made their first contribution in #482
- @levrik made their first contribution in #464
- @Maikel-Nait made their first contribution in #480
- @attilapolakovics made their first contribution in #489
- @ponjs made their first contribution in #492
- @crazyurus made their first contribution in #494
- @deining made their first contribution in #496
Full Changelog: v7.0.0...v7.1.0
v7.0.0
CRACO now supports Create React App 5.
The new documentation is live at https://craco.js.org.
v7.0.0-alpha.9
v7.0.0-alpha.8
- Added official types package
@craco/types
. - Fixed devServer config issue. #440
- Added support for Babel 7.13 compiler assumptions. #350
v6.4.5
v7.0.0-alpha.7
- Fixed babel config issues. #433
v6.4.4
v7.0.0-alpha.6
-
Utility functions have been added for webpack 5's asset modules. #387
assetModuleByName()
,getAssetModule()
,getAssetModules()
,removeAssetModules()
,addBeforeAssetModule()
,addBeforeAssetModules()
,addAfterAssetModule()
,addAfterAssetModules()
We're planning on reworking the documentation, so these functions will not be added to the existing README docs. The new documentation will be available with the release of v7.0.0.
v7.0.0-alpha.5
- The package was rewritten in TypeScript (now has built-in TypeScript declarations).
v7.0.0-alpha.3
Fix jest support #386 #378 (comment)