CLI unresponsive

The CLI is incredibly unresponsive, what’s up with that? This isn’t an urgent issue obviously, but it is a bit unappealing.

It takes nearly 3 seconds for embark to print out it’s -h option to stdout.

Are others having this issue? Is this an issue with commander.js?

λ /usr/bin/time -v embark -h

        Command being timed: "embark -h"
        User time (seconds): 2.69
        System time (seconds): 0.06
        Percent of CPU this job got: 101%
        Elapsed (wall clock) time (h:mm:ss or m:ss): 0:02.71
        Average shared text size (kbytes): 0
        Average unshared data size (kbytes): 0
        Average stack size (kbytes): 0
        Average total size (kbytes): 0
        Maximum resident set size (kbytes): 205476
        Average resident set size (kbytes): 0
        Major (requiring I/O) page faults: 0
        Minor (reclaiming a frame) page faults: 50376
        Voluntary context switches: 152
        Involuntary context switches: 4
        Swaps: 0
        File system inputs: 0
        File system outputs: 0
        Socket messages sent: 0
        Socket messages received: 0
        Signals delivered: 0
        Page size (bytes): 4096
        Exit status: 0

[iurimatias]

@nathanph What version of Embark are you using? I can confirm the 2-3 seconds on 2.3.0, but it’s instantaneous in 2.4.0

[nathanph]

Okay, the issue is that the entire project is initialized before ever running the cmd.js. This means every module required by the project has to be synchronously loaded before anything can be done.

Instead of requiring every module at the top of the index.js I’d recommend loading modules ad-hoc for each subcommand. It’s a band-aid, but it’d help.

Edit: Whoops, I’d written this before I read your response. Alrighty! Thanks!