sass-loader - npm Package Versions

4.0.0 (2016-06-27)

Bug Fixes

• Fix incorrect source map paths #250

BREAKING CHANGES

• Release new major version because the previous release was a breaking change in certain scenarios See: https://github.com/webpack-contrib/sass-loader/pull/250#issuecomment-228663059

<a name="3.2.2"></a>

3.2.2 (2016-06-26)

Bug Fixes

• Fix incorrect source map paths #250

<a name="3.2.1"></a>

3.2.1 (2016-06-19)

Bug Fixes

• Add webpack@^2.1.0-beta as peer dependency #233

<a name="3.2.0"></a>

3.2.0 (2016-03-12)

Features

• Append file content instead of overwriting when data-option is already present #216
• Make indentedSyntax option a bit smarter #196

<a name="3.1.2"></a>

3.1.2 (2015-11-22)

Bug Fixes

• Fix loader query not overriding webpack config #189
• Update peer-dependencies #182
  • node-sass^3.4.2
  • webpack^1.12.6

<a name="3.1.1"></a>

3.1.1 (2015-10-26)

Bug Fixes

• Fix missing module object-assign #178

<a name="3.1.0"></a>

3.1.0 (2015-10-25)

Bug Fixes

• Fix a problem where modules with a . in their names were not resolved #167

Features

• Add possibility to also define all options in your webpack.config.js #152 #170

<a name="3.0.0"></a>

3.0.0 (2015-09-29)

Bug Fixes

• Fix crash when Sass reported an error without file #158

BREAKING CHANGES

• Add node-sass@^3.3.3 and webpack@^1.12.2 as peer-dependency #165 #166 #169

<a name="2.0.1"></a>

2.0.1 (2015-08-14)

Bug Fixes

• Add missing path normalization (fixes #141)

<a name="2.0.0"></a>

2.0.0 (2015-08-06)

Bug Fixes

• Add temporary fix for stuck processes (see sass/node-sass#857) #100 #119 #132
• Fix path resolving on Windows #108
• Fix file watchers on Windows #102
• Fix file watchers for files with errors #134

Code Refactoring

• Refactor import resolving algorithm. (#138) (c8621a1)

BREAKING CHANGES

• The new algorithm is aligned to libsass' way of resolving files. This yields to different results if two files with the same path and filename but with different extensions are present. Though this change should be no problem for most users, we must flag it as breaking change. #135 #138

<a name="1.0.4"></a>