1. 05 Jul, 2018 2 commits
  2. 28 Jun, 2018 1 commit
  3. 26 Jun, 2018 1 commit
  4. 19 Jun, 2018 1 commit
  5. 14 Jun, 2018 1 commit
  6. 22 May, 2018 2 commits
  7. 21 May, 2018 1 commit
  8. 16 May, 2018 1 commit
  9. 13 May, 2018 2 commits
  10. 10 May, 2018 5 commits
  11. 08 May, 2018 1 commit
    • Clarify docs for --source-map. Closes #1026. · e3ab6e18
      It is not clear from the `--help` docs that `--source-map` requires a boolean or path. Passing the flag alone results in a TypeError. There's an argument to be made that passing the flag alone should imply `true`, or at the very least it should fail with a helpful error, not a cryptic TypeError. For now, this PR fixes the --help docs so that they match the README.
      Matt Kane authored
  12. 06 May, 2018 1 commit
  13. 27 Apr, 2018 1 commit
  14. 25 Apr, 2018 6 commits
  15. 24 Apr, 2018 2 commits
  16. 23 Apr, 2018 2 commits
  17. 04 Apr, 2018 1 commit
    • fix: propagate async context · 1676810c
      This is an alternative to some of the fixes in [1].
      
      Starting with Nan 2.9.0, we have the ability to propagate async context
      across async hops. Certain variants of Nan::Callback::Call are now
      deprecated to encourage use of the context presevering alternatives.
      Certain variants of Node's MakeCallback that were used internally are
      going to be deprecated in Node 10.
      
      Summary is that one should use Nan::Call for sync calls, and
      Nan::Callback::Call for async. The latter expects an async resource
      corresponding to the async operation to be provided at the call time.
      
      This patch fixes things up so that 1) node-sass isn't using any
      deprecated APIs, and 2) properly propagates async context for async
      callbacks by creating async resources in the appropriate places.
      
      [1]: https://github.com/sass/node-sass/pull/2295
      Ali Ijaz Sheikh authored
  18. 03 Apr, 2018 1 commit
  19. 29 Mar, 2018 1 commit
  20. 17 Mar, 2018 7 commits