label-studio-frontend icon indicating copy to clipboard operation
label-studio-frontend copied to clipboard

Failed to install v1.8.0

Open Wigithub1201 opened this issue 1 year ago • 13 comments

Hi

My system is Windows 10, and I executed the commands ‘npm install @heartexlabs/label studio’ and ‘yarn add @heartexlabs/label’ studio, but the dependent packages were not successfully installed. What is the reason @makseq

image

Wigithub1201 avatar Jun 07 '23 07:06 Wigithub1201

There are only images and no build folder on the NPM package image

Wigithub1201 avatar Jun 07 '23 07:06 Wigithub1201

Same error here. We cannot install via npm the 1.8.0 version. 1.4.0 still works fine

lbelmonte-ag avatar Jun 08 '23 11:06 lbelmonte-ag

I have the same error on Linux. I tried to build from source, but could not find a way to properly export the 'LabelStudio' module.

YukiYamamoto228 avatar Jun 13 '23 08:06 YukiYamamoto228

Hi have you found a solution? I am facing the same issue unfortunately

bigabig avatar Jun 19 '23 13:06 bigabig

Same problem here! hopefully the LSF team can resolve this! thanks alot!

Zensome avatar Jun 20 '23 09:06 Zensome

npm install @heartexlabs/label-studio --ignore-scripts

ruanhan avatar Jun 30 '23 10:06 ruanhan

https://github.com/heartexlabs/label-studio-frontend/issues/1488

ruanhan avatar Jun 30 '23 10:06 ruanhan

same problem here

gigaenr-bh avatar Jul 06 '23 10:07 gigaenr-bh

Any chance to fix this?

jheyming avatar Aug 04 '23 19:08 jheyming

Same error here

Oguerisck avatar Oct 17 '23 14:10 Oguerisck

Has anyone found a fix for this?

I am facing same error

npm ERR! code 127 npm ERR! path /Users/user/Documents/temp/node_modules/@heartexlabs/label-studio npm ERR! command failed npm ERR! command sh -c sh scripts/postinstall.sh npm ERR! sh: scripts/postinstall.sh: No such file or directory

Screenshot 2024-01-31 at 3 23 58 PM

animeshpaul123 avatar Jan 31 '24 09:01 animeshpaul123

Has anyone found a fix for this?

I am facing same error

The package is broken (not uploaded correctly) in NPM repository. If you want to use it, I'd recommend pulling the repository and build the package not with npm but with yarn.

tl;dr try to replicate the steps from GitHub CI and pay attention to versions used. https://github.com/HumanSignal/label-studio-frontend/blob/master/.github/workflows/build_bundle.yml

tranhd95 avatar Feb 12 '24 13:02 tranhd95

Is there a workaround for this other than building the package locally and pointing to that? https://github.com/HumanSignal/label-studio-frontend/issues/1488 is also open with the same issue

markotonic avatar Feb 22 '24 10:02 markotonic