-
Notifications
You must be signed in to change notification settings - Fork 8
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
Client build broken #14
Comments
@aashish24 @thewtex Seems I need more permission in order to be able to assign issues to myself on this repository. Can one of you make me part of "write access", "admin access", or "owners" team on this organization? According to this SO, that would do the trick. |
The previous package lock did not match the required packages and prevented, e.g., node-sass from being installed. Fixes OpenImaging#14
@scottwittenburg according to the Collaborators section, you have Admin access, but have not yet accepted the invitation to the repository (there should be an email in your inbox). |
Whoops, you're right, there was an invitation in my inbox. When I received it, I just followed the link to the repo instead of viewing the invitation. Now, unfortunately, it has expired, sorry. Can it be resent or refreshed or something? |
@scottwittenburg 👍 resent |
Thanks I accepted it this time. |
Following the developer setup instructions, the step building the client application (
npm run serve
) fails with a bunch of errors like the following:Complete error log attached.
client-build-error.txt
The text was updated successfully, but these errors were encountered: