1. 28 Jun, 2013 1 commit
  2. 17 Jun, 2013 2 commits
  3. 12 Jun, 2013 4 commits
  4. 08 Jun, 2013 2 commits
  5. 06 Jun, 2013 3 commits
  6. 29 May, 2013 4 commits
  7. 23 May, 2013 1 commit
  8. 22 May, 2013 1 commit
  9. 13 May, 2013 3 commits
    • Added link to grunt-sass · 1177212d
      Andrew Nesbitt authored
    • Merge pull request #100 from nyteshade/master · 4779d70c
      Cleaner, non-breaking, path handling for source and destination with a shared root
      Andrew Nesbitt authored
    • Cleaner path handling using a root value · 2fe930f3
      If a root value is supplied in the options for this middleware, then the dest and src values are relative this this location. They should also use the standard URI path separators.
      
      When this is done, the setup looks something like this (for express):
      
      ```javascript
        app.use(sass.middleware({
          src: '/sass',
          dest: '/css',
          root: path.join(__dirname, 'public')
        }));
      ```
      
      A call to /css/some/path/file.css will build the paths such as
      ```
      dest: /css/some/path/file.css
      src:  /sass/some/path/file.scss
      ```
      The old version of the code, given a setup of the following:
      
      ```javascript
        app.use(sass.middleware({
          src: '/sass',
          dest: '/css'
        }));
      ```
      
      would have generated paths such as:
      ```
      dest: '/css/css/some/path.css'
      src: '/sass/css/some/path.scss'
      ```
      You should be able to see the unnecessary '/css/' path structures within. This just makes things messy and for no real good reason.
      Gabriel authored
  10. 12 May, 2013 2 commits
  11. 10 May, 2013 10 commits
  12. 09 May, 2013 2 commits
  13. 03 May, 2013 2 commits
  14. 02 May, 2013 3 commits