Skip to content

Releases: dferber90/jest-transform-css

v6.0.3

21 May 11:17
64fda7b

Choose a tag to compare

  • make compatible with VSCode debugger (fixes #31 via #32, thanks @hheimerd)

v6.0.1

13 Jan 21:13
c43633e

Choose a tag to compare

Bug fix

  • escape backslashes in windows paths - thanks @albekov (#26)

v6.0.0

05 Oct 05:24
00df393

Choose a tag to compare

  • Upgraded postcss-load-config to latest version in #23, thanks @Yankovsky

BREAKING CHANGE

Your .postcssrc file might need to be adapted as postcss-load-config dropped support for the sync API and for Node.js 12 & 10.

v5.0.0

14 Sep 06:05
4191027

Choose a tag to compare

BREAKING CHANGE

  • dropped support for jesttransformcss.config.js in favor of transformer config

You no longer need a jesttransformcss.config.js file. Instead, configure your transform directly.

See #22 for more information.

massive thanks to @Yankovsky for coming up with & implementing this improvement

v4.0.1

01 May 19:54
411c782

Choose a tag to compare

  • make compatible with Jest v28, thanks @3c1u

v4.0.0

03 Apr 13:49
fd7c965

Choose a tag to compare

v3.0.0

18 Nov 05:20
afb8c5e

Choose a tag to compare

v2.1.0

24 Sep 05:12
244e4fa

Choose a tag to compare

  • Added a generateScopedName config option to jesttransformcss.config.js (#7, thanks @tomrule007)

v2.0.0

24 Sep 10:03
65edbc1

Choose a tag to compare

Fixed

  • d35fe66 remove rootDir from cache key

Breaking

  • fea1e8d default to regular CSS (CSS Modules are now opt-in)

Upgrade Guide

So far CSS Modules were enabled by default. They are now opt-in. Add a configuration file called jesttransformcss.config.js at your project root to and add the following content to activate them:

// jesttransformcss.config.js

module.exports = {
  modules: true
};

Notice that you can also pass a function to modules to determine the mode depending on the file. See the README for more information.

v1.1.0

23 Sep 19:25
05f2811

Choose a tag to compare

Added

Changed

Upgrade guide

postcss-load-config and postcss-modules are no longer peerDependencies, so they can be removed from consuming projects not using them themselves.