New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create project brakes autoloader if target dir is current (maybe) #288
Comments
Not sure if "." is even possible with composer create-project. You are using composer 1.3.2, maybe you could try it again the latest release (1.4.x). |
Updated and it works the same.
|
@iBobik have you ever found a solution? Experiencing the exact same issues. |
Hi,
I am do not remember.
I use it in this project and how-to in readme there works. Try it:
https://github.com/iBobik/drupal-composer-docker
|
For future reference: It started working locally when I removed caps from my path (or moved the project to a case-sensitive volume on mac):
|
I'm getting this error on a Windows machine. |
Also does not work when adding a relative path to the creation directory. So using There are other tickets about this, but none of them make this connection. My workaround is to just create the project in a subdirectory, them move the subdirectory where you need it. |
This pull request/issue has been inactive for over a year and is being closed due to inactivity. If the issue still persists or the contribution is still relevant, please feel free to reopen it or create a new one. Thank you for your understanding and your contributions to the project! |
Something strange happened - I tried to create new project in current directory (
.
) and it created project with not working autoloader. Then I removed it and created the same in subdirectory (drupal-new
) with the same parameters in the same Docker container, but errors disappeared.Now it works for me and I does not have motivation to debug it, but I am curious why it happened. Also it could be potential technical bug, UX bug or incomplete docs.
Here is my shell log. Sorry it is not trimmed, but I am scared I could trim something important what I does not know it is important.
The text was updated successfully, but these errors were encountered: