Using LabelStudio frontend only

[nikhilguptagl]

Hi, I was using LabelStudio frontend in my project as a npm library. I understand that it was deprecated last year. And I am seeing that now in this repo we have frontend and backend both. Is there any way, I can use LabelStudio frontend only without backend and I can aur custom backend for this ?

[heidi-humansignal]

Hello,

Thank you for contacting Label Studio,

I am afraid to inform you that as of Label Studio 1.11.0, the standalone LSF npm package was officially deprecated and is no longer maintained or supported as a separate distribution. Now, Label Studio is developed as an integrated monorepo where the backend and frontend are tightly coupled.

If you truly need to run LSF without the official backend, you have two main approaches:

1. Build From Source (Monorepo):
   • You can clone the Label Studio repository and look under “web/libs/editor.”

• Manually build the frontend portion for your own environment.

• But please note, this requires a custom integration layer between the frontend and any backend you develop yourself. Label Studio no longer provides official documentation for this setup.
2. Use an Older Version of LSF:
• If you want to rely on the deprecated LSF npm package, you could pin an older version (e.g., versions before 1.11.0).

• However, these versions receive no further updates or fixes, and you’d still have to handle all backend logic and data handling yourself.
Because of deprecated support, we recommend using the fully integrated Label Studio platform if at all possible. Should you still want to proceed with a custom solution, you’d need to rely on manual building and maintain your own custom reconciliation between LSF and your backend.
Let me know if you have any follow-up questions!

Comment by Oussama Assili
Workflow Run

[nikhilguptagl]

Thanks for the response,
However, I have installed the packages inside web/libs/editor but I see there is no way, I can run the files as there are no commands inside package.json.

I see we have to install the packages inside web/ folder and then run the server from there to run the frontend part of it? Is that true ?

I have to use the frontend package and deploy it on higher environments so that content engineers can use it. Can you provide any optimal solution for this ?