I wanna import sass in my react-app, I follow the user guide and found if I don't new a .scss file in project, npm start will cause wrong.

[TomIsion]

Description

I follow the user guide, wanna import sass in my project. After I change the npm scripts settings in package.json, I didn't new a .scss file in my project. Then npm start caused error.

> react-list@0.1.0 build-css /Users/tom/Work/React/react-list
> node-sass-chokidar --include-path ./src --include-path ./node_modules src/ -o src/

No input file was found.

npm ERR! Darwin 16.6.0
npm ERR! argv "/usr/local/Cellar/node/7.5.0/bin/node" "/usr/local/bin/npm" "run" "build-css"
npm ERR! node v7.8.0
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-list@0.1.0 build-css: `node-sass-chokidar --include-path ./src --include-path ./node_modules src/ -o src/`

But I new a .scss in src folder it works well. No errors anymore.

Expected behavior

I wanna even if I don't new a .scss file then npm start won't cause wrong.

Environment

As the wrong info shows.

Then, specify:

1. Operating system:
2. Browser and version:

Mac OSX

[Timer]

/cc @michaelwayman

[michaelwayman]

@TomIsion I have raised this issue with node-sass-chokidar.
You can find it here

I am able to reproduce the issue, basically when there are no .scss files in the ./src folder the command you are running will throw a warning saying there are no input files, but then also throws an npm error. I'm assuming the behavior you were expecting was to get the warning without the npm error. I should be able to fix this this weekend, thanks for reporting this.

[TomIsion]

👍

[michaelwayman]

This issue has been resolved with the latest PATCH version of node-sass-chokidar.
Instead of raising an error, it now prints a simple warning saying to input files can be found.
@TomIsion
@Timer I think this can be closed.

[gaearon]

Awesome, thanks for followup!