lb export-api-def never returns in NodeJS command prompt about loopback-cli HOT 5 CLOSED

Hello, thank you for reporting this issue. Is it possible that your application is allocating resources running in background (e.g. a connection pool used by a database driver behind a LoopBack datasource) that's blocking the process from exiting? You can verify this assumption by running the following command in your application/project directory:

node -e "require('./')"

If the command hangs, then it's your application what's blocking lb export-api-def from exiting. This can be fixed e.g. by modifying lb export-api-def to explicitly kill the process once the spec file was written - would you like to contribute the fix yourself?

from loopback-cli.

Thanks for the feedback, I understand now why I was seeing a hanging redis connection when running the lb export-api-def command with all debug strings enabled :) (I have a few bits of redis code inside my server)

No problem for making the fix, I'll submit a PR

from loopback-cli.

I've made a PR, but I'm not sure how to test this feature. More specifically, how to generate a app that never finishes loading using the template from loopback-workspace. Let me know if you have something obvious in mind.

from loopback-cli.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from loopback-cli.

Closing as fixed by strongloop/generator-loopback#316

from loopback-cli.