The seed projects referenced by the cleverstack-cli has names as cleverstack-angular-seed, whereas the repos themselves are named as angular-seed in their respective package.json files. This prevents any operation that requires the package names, such as clever serve.
I followed the documentation as it was and got stuck at clever serve, till I fixed this.
Also, it's worthwhile looking at how we can abstract out these constants without hardcoding them everywhere.
Sorry about that @ncthis i was in the middle of changing the repo's over and NPM was having some issues - the fix has already been pushed into version 0.0.50
The seed projects referenced by the
cleverstack-cli
has names ascleverstack-angular-seed
, whereas the repos themselves are named asangular-seed
in their respectivepackage.json
files. This prevents any operation that requires the package names, such asclever serve
.I followed the documentation as it was and got stuck at
clever serve
, till I fixed this.Also, it's worthwhile looking at how we can abstract out these constants without hardcoding them everywhere.