Closed driesvints closed 9 years ago
Ah, apparently you ran this in a directory that wasn't a Composer project itself.
Funny that I didn't anticipate that use-case, it's quite straightforward. Probably because I started out with the objective of replacing Workbench, which always ran inside Composer projects (a Laravel install).
Thanks for bringing this to my attention, it will be fixed soon.
P.S.: The studio.json
file is important for autoloading when developing a library as part of a larger project (when you don't yet want to have it in the vendor directory). It lets my Composer plugin know that your libraries dependencies should be autoloadable from the main application, too.
Fixed. Again, thanks for the report.
This should be available under dev-master
and in the next release (0.9.6).
Thanks! :)
You're welcome.
I must correct myself, though: it's in 0.9.x-dev
, not dev-master
. I mixed up my branches...
Reproduce: run
studio create <dir name>
--> throws RuntimeException.Here's the console output:
I also now have a
studio.json
file in the directory where I called the command with the following contents:I don't know what that file does or why it was created. I guess it gets removed again at the end of the install process and wasn't because the installer never reached the end?
Anyway, looks like the skeleton got set up nicely. Great package, thanks! :)