Guy Bedford

@samccone yeah that works perfectly actually. I did also try raising the memory limit here but it still ends up going over 1GB which seems odd for a 50MB file.

Just to clarify the build situation here. Basically we have the following options: 1. Use Traceur to compile the modules into a single file that can work in production. We...

I'll most likely need to get a PR into https://github.com/aaronfrost/grunt-traceur to get this updated. I'm actually giving a talk on this workflow early next month, so this would be ideal...

I'm keen to see this grunt workflow, unfortunately I won't have time to work on grunt-traceur until later this month now, which is a little annoying as ideally that is...

@MylesBorins because of backporting constraints, I don't think lexer features should be changed. Object detection is just patchy unfortunately. I think we should only stick to updates for parser bug...

The problem is we cannot expect users to track fine-grained exports detection rules as being compatible or not. For example if we made the lexer support these named exports in...

Yes, although the difference here is parser internals are difficult to communicate as features, in the same way that versioning parsers or transformers is hard.

Good to hear from you @phated, and thanks for the quick response. I was unable to replicate this again in my own tests, so please don't spend any time digging...

Thanks, I'm still struggling to get that replication from the original issue, but will keep you posted.

I still haven't got a replication on this, but a user [just posted](https://github.com/jspm/jspm-cli/issues/1338#issuecomment-177940126) they are getting this with a NODE_PATH of `C:\Users\AppData\Roaming\npm\node_modules`.