-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
npm ERR! command sh -c -- sh scripts/postinstall.sh #4344
Comments
Hello Cyurainya, Is this for the front-end repo that your are trying to build LSF? |
thx for your answer.
|
@Cyurainya were you able to resolve this issue? I'm facing the same issue while installing in nuxt3 using yarn. |
🥲not yet |
@Cyurainya what are your observations so far? any idea about the origin of this issue? |
I didn't have time to fix. Finally decided to revamp his frontend project |
having the same issue on MacOS 22.5.0. Also trying to install labelstudio using npm. Just initialized the project using npm init so this is the first dependency I am trying to install. Attached the complete log. |
Is it possible you can try |
Yes. I'm trying to install LSF. I've tried with npm and yarn as well. no luck. Also I tried to use it as external script file but seems like library doesn't exist on mentioned link. |
hey, I'm experiencing the same issue
|
any update on this guys , i used linux its working but in windows its not soo,same issue |
Check your package.json and package-lock.json. After making the correction, the error disappeared. |
I have tried to remove the prepare on package.json, it worked for me now |
Hi folks. I have the same issue. Here's my minimal failing example:
gives
I can install other packages without issue. Is there something silly I'm missing? nvm 0.39.3 |
The issue is being widely reported here - HumanSignal/label-studio-frontend#1439 The issue is with the https://www.npmjs.com/package/@heartexlabs/label-studio/v/1.8.0 |
Anyone knows how to fix this? |
when I enter the command
npm install @heartexlabs/label-studio
the terminal came out the error:
my node version is v16.18.1
The text was updated successfully, but these errors were encountered: