Builder dies on with "Unexpected token import " about builder HOT 7 CLOSED

The path does seem a little strange there, perhaps this could be a Windows bug.

Is there any way you can share a reproducible part of the failure at all? It would help a lot to look into it.

from builder.

Ok, I have a test project up that reproduces the problem: https://github.com/outdooricon/my-projectA-name . Just run npm install and then gulp sys-build. Also, in case it matters, my project path for this is C:\Users\Johnathon\Projects\my-projectA-name. My current error output is:

C:\Users\Johnathon\Projects\my-projectA-name>gulp sys-build                                                              
[06:04:21] Using gulpfile ~\Projects\my-projectA-name\gulpfile.js                                                        
[06:04:21] Starting 'sys-build'...                                                                                       
[06:04:21] Finished 'sys-build' after 403 ms                                                                             
Build error                                                                                                              
[ 'C:\\Users\\Johnathon\\Projects\\my-projectA-name\\app\\scripts\\testFolder/otherTest.js:1:1: Unexpected token import',
  'C:\\Users\\Johnathon\\Projects\\my-projectA-name\\app\\scripts\\testFolder/otherTest.js:1:8: Semi-colon expected',    
  'C:\\Users\\Johnathon\\Projects\\my-projectA-name\\app\\scripts\\testFolder/otherTest.js:1:10: Semi-colon expected',   
  'C:\\Users\\Johnathon\\Projects\\my-projectA-name\\app\\scripts\\testFolder/otherTest.js:1:15: Semi-colon expected',   
  'C:\\Users\\Johnathon\\Projects\\my-projectA-name\\app\\scripts\\testFolder/otherTest.js:3:1: Unexpected token export',
  'C:\\Users\\Johnathon\\Projects\\my-projectA-name\\app\\scripts\\testFolder/otherTest.js:3:8: Semi-colon expected' ]   

Final note, rarely but sometimes i can get this to build successfully... it almost acts like an async problem..

from builder.

Thanks, that helped a lot.

Yes this was a collission of sorts. You will find if you keep running the build that it sometimes does work. For now that would be my suggestion!

I've added a fix in ModuleLoader/es-module-loader@32b9c9f.

I will run the release process as soon as I can and update here when it's in SystemJS builder.

from builder.

Ok I've published a 0.2.3 with the fixes. Let me know if that works for you.

from builder.

That did the trick! I'm intrigued by the solution, without that did traceur not know to parse modules?

from builder.

There are places in SystemJS builder where it has to switch the options to script parsing, while the module loader needs module parsing. Traceur does tend to have some options collissions in the way it handles options unfortunately, so it is necessary to set all options explicitly.

from builder.

Interesting... thanks for you help!

from builder.