Skip to content
This repository has been archived by the owner on Jan 16, 2018. It is now read-only.

How would you ignore harmony features for the server? #1

Open
mtscout6 opened this issue Jan 7, 2015 · 3 comments
Open

How would you ignore harmony features for the server? #1

mtscout6 opened this issue Jan 7, 2015 · 3 comments

Comments

@mtscout6
Copy link

mtscout6 commented Jan 7, 2015

Is there a configuration option I'm missing?

Here's my output:

Child server:
    Hash: 6d88699fa57e97fc02a2
    Version: webpack 1.4.15
    Time: 21ms
       [0] ./lib/server.js -1 [built] [failed]

    ERROR in ./lib/server.js
    Module parse failed: /Users/smithm/dev/node-blog/lib/server.js Line 13: Unexpected token *
    You may need an appropriate loader to handle this file type.
    |
    | // x-response-time
    | app.use(function *(next){
    |   var start = new Date;
    |   yield next;

I plan to run my server with the --harmony flag.

@sokra
Copy link
Member

sokra commented Jan 8, 2015

This is not supported right now... but I plan to upgrade the esprima parser to harmony once it's stable enough...

@mtscout6
Copy link
Author

mtscout6 commented Jan 8, 2015

Roger that, I'll have to check it out when you get that up and running. Thanks!

@maletor
Copy link

maletor commented Apr 2, 2015

Why couldn't you use babel-loader instead of jsx-loader? That will give you a lot more ES6 features.

Node is pretty much guaranteed to throw a message about the file being over 100KB, should we be concerned about that or can it handle it?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants