Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

node-sass won't --stdout (argument check fails) #626

Closed
appsforartists opened this issue Jan 14, 2015 · 3 comments
Closed

node-sass won't --stdout (argument check fails) #626

appsforartists opened this issue Jan 14, 2015 · 3 comments

Comments

@appsforartists
Copy link

This doesn't work as expected:

> node-sass --stdout ./b.scss 
Compile .scss files with node-sass.
Usage: node /usr/local/bin/node-sass [options] <input.scss> [<output.css>]

Options:
  --output-style     CSS output style (nested|expanded|compact|compressed)  [default: "nested"]
  --source-comments  Include debug info in output (none|normal|map)         [default: "none"]
  --source-map       Emit source map                                      
  --include-path     Path to look for @import-ed files                      [default: "/Users/bresimpson/Projects/multiWebstore/merchants/petsmart/styles"]
  --image-path       Path to prepend when using the image-url(…) helper     [default: ""]
  --precision        The amount of precision allowed in decimal numbers     [default: 5]
  --watch, -w        Watch a directory or file                            
  --output, -o       Output css file                                      
  --stdout           Print the resulting CSS to stdout                    
  --help, --help     Print usage info                                     

Argument check failed: function (argv){
    if (argv.help) { return true; }
    if (argv._.length < 1) { return false; }
  }

This does:

node-sass ./b.scss ./garbage.css

Using [email protected] and [email protected].

@am11
Copy link
Contributor

am11 commented Jan 15, 2015

You should also try with the latest release, [email protected].

@xzyfer
Copy link
Contributor

xzyfer commented Jan 15, 2015

@am11 what are your thoughts on removing the --stdout and making it the
default behaviour if an output directory or file isn't supplied. This the
behaviour of Ruby sass and Libsass.
On 15 Jan 2015 11:57, "Adeel Mujahid" [email protected] wrote:

You should also try with the latest release, [email protected].


Reply to this email directly or view it on GitHub
#626 (comment).

@am11
Copy link
Contributor

am11 commented Jan 15, 2015

This makes sense to me. Even other node based compilers (Less etc.) also exhibit this behavior.

@am11 am11 closed this as completed Jan 18, 2015
jiongle1 pushed a commit to scantist-ossops-m2/node-sass that referenced this issue Apr 7, 2024
Correctly handle nested feature queries
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants