-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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
[BUG] AdminLTE fails to install with yarn and custom folder #2561
Comments
Thanks for reporting this issue, I'll check this within the next days. |
I may found the problem, --modules-folder 'vends' everything works like it should after some tests, I created a blank folder and added this to .yarnrc by hand --modules-folder vends and without the single-quotes yarn add failed. Please check this 😄 |
Thanks for the quick response! I did what you said and it worked perfectly. But, I believe the quotes should not be required. Every other package I have works without them. Plus, many examples of the modules-folder option do not use quotes. On the other hand the only official docs we have is this and it is not clear about the behavior at all. Also as a test I tried passing --modules-folder via cli and it behaves exactly the same as putting it in .yarnrc. Thanks again for the support!! |
If I remember right, the quote set it to a string and without it's a constant that some scripts use as string, I didn't figured out how I can require it correctly for this behavior. And I personally set always paths as string with quotes, only if I'm lazy not 😃 Also this look like yarn itself cause this problem and not load the node modules correctly.
No problem 😄 I close this issue. |
Sorry for coming back. But when I said it worked I was not quite right. When I put the quotes in my .yarnrc, yarn install the packages to the node_modules folder. That's why it installed the package. With double quotes I have the same error as not using quotes. |
That's strange :/ I've found this issue yarnpkg/yarn#5200 on yarn's repo that's may related to this. |
Thanks again. I will try that. |
Hello, have you solved this issue? I am still getting errors.
|
@juniwalk Try to remove your node_modules folder and reinstall with yarn again. |
I have custom folder in www/vendor so my assets are in domain root, without the custom folder it works. I tried everything that was mentioned above to be tried and nothing worked. So I did remove the folder to no avail. |
I solved it by adding these two settings in my .yarnrc file pointing to my custom directory. Note that the paths have to be absolute.
|
@FelipeEmerim Well I don't like hard coding absolute path there but it really does work! Thank you. |
@juniwalk Me neither, but it is the only way I got it working. It seems to be a problem with yarn as mentioned above. |
To Reproduce
Expected behavior
The package should install
Screenshots
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: