This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of node-sass.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
In v3.9.0 started publishing our test suite to npm. This caused issues for users on systems with poor unicode support or file path length limits. This changed was reverted until we could engineer a better solution.
In this release we've migrated our test suite to a separate npm module which is now a devDependency. With change users will only download the test suite on an opt-in basis by explicitly install devDependencies.
Hello lovely humans,
node-sass just published its new version 3.10.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of node-sass. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
Sass Spec
In v3.9.0 started publishing our test suite to npm. This caused issues for users on systems with poor unicode support or file path length limits. This changed was reverted until we could engineer a better solution.
In this release we've migrated our test suite to a separate npm module which is now a devDependency. With change users will only download the test suite on an opt-in basis by explicitly install devDependencies.
@nschonni, @xzyfer, #1686
Misc
The new version differs by 60 commits .
aec7049Update changelog24e2e2c3.10.0128646eMerge pull request #1717 from nschonni/issue-template-updateeb8df02Update ISSUE_TEMPLATE with Bootstrap format105cca2Merge pull request #1711 from nschonni/util-extent-to-object-assignccfbbcbMerge pull request #1698 from nschonni/update-spec-runnerb27386dSwitch sass-spec submodule for NPM0c709c1Merge pull request #1700 from nschonni/eslint-updates61f42deReplace util._extend with lodash.assign6dda1deMerge pull request #1703 from sass/revert-1688-feat/publish-tests0cdee5cRevert "Publish tests to npm"72af63e3.9.34cc86f7Revert to v3.9.0003819dsass-spec runs recursively as suites05105adBump ESLint to 3.x and fix errorsThere are 60 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade