Skip to content
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

Using LabelStudio frontend only #6957

Open
nikhilguptagl opened this issue Jan 24, 2025 · 1 comment
Open

Using LabelStudio frontend only #6957

nikhilguptagl opened this issue Jan 24, 2025 · 1 comment

Comments

@nikhilguptagl
Copy link

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
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants