-
Notifications
You must be signed in to change notification settings - Fork 15
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
Path issue with mix on fresh clone #5
Comments
Hi @wdelfuego No, I didn't started this feature yet. Anyway, as you said, this error is just because of difference of custom paths in my computer system and yours.
As you can see, my local package is placed in that path and I'm using nova from that vendor (vendor of root folder) which is not correct 😁, but I'm OK with it for now. |
Good to know 👍 You don’t think it’d be better for the project to come in a directly runnable state? Imo it’d be a shame to lose contributor time to needless debugging when they’re first looking into the project. |
Yes, you are right. But I developed this package in hurry to use it in one of my own projects. so I decided to keep it as simple as I can. And FYI, I started to work on |
While this issue lives in the codebase, anyone who is possibly interested in forking/contributing will run into this bug by default and will have to investigate themselves. Until the repo is fixed I'd at least leave this issue open so people who run into it can easily find the solution here. |
Issue reopened 😁 And I will fix it later. maybe 2 or 3 weeks later |
I just forked this repo because I want to play around with adding a search field (let me know if this is something you've already finished 😄).
But I couldn't run
npm run
on the freshly cloned tool until I changed line 19 of itswebpack.mix.js
file from:to:
Before I made that change, I got errors of this type:
Not sure if this is an issue caused by custom paths on my system or yours, I'll gladly create a pull request for this change if you think it should be changed.
The text was updated successfully, but these errors were encountered: