Why did my code start breaking in v3.5 #1474

xzyfer · 2016-04-23T05:57:27Z

Due to the amount of people creating issues I have written a blog post about this.

https://medium.com/@xzyfer/why-node-sass-broke-your-code-and-semver-1b3e409c57b9#.xkbqzng6a

Fix #278 More info can be found here: sass/node-sass#1474

…mport path probably due to node-sass 3.5 breaking change sass/node-sass#1474 related issues: sass/node-sass#1592 brunch/sass-brunch#111 brunch/brunch#1402

…rsing Fix `functional_schema` parsing ending with interpolation

cgrinds mentioned this issue May 3, 2016

Broken bar and line charts beancount/fava#278

Closed

aumayr added a commit to beancount/fava that referenced this issue May 4, 2016

Pin node-sass version to 3.4.2

c6d5575

Fix #278 More info can be found here: sass/node-sass#1474

This was referenced Jun 13, 2016

render error callback not called on import path error #1592

Closed

breaking change in node-sass import without a major bump cascading as a breaking change in sass-brunch too brunch/sass-brunch#111

Closed

xzyfer mentioned this issue Jul 5, 2016

Assigning variables in @if statement #1623

Closed

nschonni mentioned this issue Aug 24, 2016

Webpack segmentation faults for newer versions of node-sass #1676

Closed

nschonni closed this as completed Sep 19, 2016

jiongle1 pushed a commit to scantist-ossops-m2/node-sass that referenced this issue Apr 7, 2024

Merge pull request sass#1474 from mgreter/bugfix/functional-schema-pa…

af8365d

…rsing Fix `functional_schema` parsing ending with interpolation

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Why did my code start breaking in v3.5 #1474

Why did my code start breaking in v3.5 #1474

xzyfer commented Apr 23, 2016 •

edited by mgreter

Loading

Why did my code start breaking in v3.5 #1474

Why did my code start breaking in v3.5 #1474

Comments

xzyfer commented Apr 23, 2016 • edited by mgreter Loading

xzyfer commented Apr 23, 2016 •

edited by mgreter

Loading