When installed with CLI, bin points to non-existent path about generator-node HOT 9 CLOSED

Ugh, yeah.

That generator really isn't great. It needs to define patterns for options and arguments in it's constructor. And it need to be smarter.

from generator-node.

I'll look into this. Try running gulp babel and npm link again?

That generator really isn't great. It needs to define patterns for options and arguments in it's constructor. And it need to be smarter.

Yep. I totally agree.

from generator-node.

That creates the dist/cli.js, also npm link works. But when I try to run the module, this happens:

C:\Projects\testapp-node-cli
λ gulp babel
[23:14:11] Using gulpfile C:\Projects\testapp-node-cli\gulpfile.js
[23:14:11] Starting 'babel'...
[23:14:11] Finished 'babel' after 175 ms

C:\Projects\testapp-node-cli
λ npm link
C:\Users\<user>\AppData\Roaming\npm\testapp-node-cli -> C:\Users\<user>\AppData\Roaming\npm\node_modules\testapp-node-cli\dist\cli.js
C:\Users\<user>\AppData\Roaming\npm\node_modules\testapp-node-cli -> C:\Projects\testapp-node-cli

C:\Projects\testapp-node-cli
λ testapp-node-cli
C:\Projects\testapp-node-cli\lib\index.js:2
export default {};
 ^^^^^^
SyntaxError: Unexpected reserved word
    at exports.runInThisContext (vm.js:73:16)
    at Module._compile (module.js:443:25)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (C:\Projects\testapp-node-cli\dist\cli.js:15:10)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)

from generator-node.

That creates the dist/cli.js, also npm link works.

Well, that's the expected behaviour. When using babel you of course have to compile your code first.

But when I try to run the module, this happens:

This is a bug not related to the CLI. The problem is that our main in the generated package.json points to lib/index.js, which is a problem when using babel as that's the source version not the compiled version.

from generator-node.

I see, thanks for looking into this. 👍

Also, I would like to mention that as a new user I was a bit confused by this issue since this wasn't happening when I ran yo node:cli (without --no-babel, doesn't it default to true?), it created only lib/cli.js and everything worked.

from generator-node.

@petersandor This is not an issue on your side. This generator output is broke. We'll fix it.

from generator-node.

@arthurvr You assigned yourself that ticket. I think it's working fine now, can you double check and close it if that's the case? Thanks :)

from generator-node.

Looks alright now. Nice work @SBoudrias :)

from generator-node.

👍

from generator-node.