Skip to content

Commit

Permalink
pin node-sass to 1.0.3
Browse files Browse the repository at this point in the history 
because of sass/node-sass#497
  • Loading branch information
@sindresorhus
sindresorhus committed Oct 31, 2014
1 parent 579c0d1 commit a790771
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion package.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@
"dependencies": {
"chalk": "^0.5.1",
"each-async": "^1.0.0",
"node-sass": "^1.0.0",
"node-sass": "1.0.3",
"object-assign": "^1.0.0"
},
"devDependencies": {
Expand Down

1 comment on commit a790771

@mgol
Copy link

@mgol mgol commented on a790771 Oct 31, 2014

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aren't such changes dangerous? Some people may already start relying on node-sass 1.1.x features via grunt-sass and then, if they have "grunt-sass": "~0.16.0" on the next npm install their build will start failing. It seems that pinning to a release older than the latest minor bump of a dependency is risky when done in a patch release.

Please # to comment.