search

HoriSun / closure-compiler

Automatically exported from code.google.com/p/closure-compiler
0 stars 0 forks source link

stdin handling broken with closure_entry_point #1292

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

Try stdin instead of --js parameter. closure_entry_point will not sort stdined 
files.

What is the expected output? What do you see instead?

stdin should work exactly as --js

Original issue reported on code.google.com by dan...@steigerwald.cz on 1 Apr 2014 at 8:18

GoogleCodeExporter commented 9 years ago 
Can you give an example command-line of how you use this?  Are you mixing --js 
and stdin?

Original comment by concavel...@gmail.com on 5 Apr 2014 at 11:56

GoogleCodeExporter commented 9 years ago 
That's how I am using it: 
https://github.com/steida/gulp-closure-compiler/blob/master/index.js
No, I am not mixing --js with stdin.

Original comment by dan...@steigerwald.cz on 29 Apr 2014 at 3:05

GoogleCodeExporter commented 9 years ago 
Sorry, I'm not very familiar with reading Node-style code, or maybe I'm just 
missing the relevant spot. But it looks like you are using --js (line 25) and I 
don't see you passing JS to the compiler's stdin anywhere. Can you point out 
where that's happening?

Original comment by tbreisac...@google.com on 29 Apr 2014 at 4:44

GoogleCodeExporter commented 9 years ago 
I don't understand what you are expecting here.  There can only be a single 
"stdin" file, so any input there would be "sorted"  as there would only be one.

Original comment by concavel...@gmail.com on 1 May 2014 at 3:58

GoogleCodeExporter commented 9 years ago 
Issue tracking has been migrated to github. Please make any further comments on 
this issue through https://github.com/google/closure-compiler/issues

Original comment by blic...@google.com on 1 May 2014 at 6:31

GoogleCodeExporter commented 9 years ago

Original comment by blic...@google.com on 1 May 2014 at 6:34