-
Notifications
You must be signed in to change notification settings - Fork 382
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Prepare 2.3.0-beta.1 with node-sass@3.5.0-beta.1
- Loading branch information
Showing
1 changed file
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I'm curious, why is this strictness needed for the
node-sass
version?3.5.x
was just released and caused a regression for us, but since we use npm3, we can put~3.4.x
in our package.json to pin it. I'm worried now though that if you do this, we'll be bumped back to3.5
again once you release2.3.x
, so we'll need to pin togulp-sass@2.2.x
too.