[GH-ISSUE #4568] [Feature Request] Samber lo version up

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#3611

gitea-mirror commented

2026-05-05 14:19:11 -06:00

Owner

Originally created by @Guiwoo on GitHub (Nov 30, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4568

Describe the feature request

Feature Request: Use FRP as a Library and Update samber/lo Dependency

English Summary

Problem:
Currently, the project uses samber/lo as a dependency, but with the release of newer versions, compatibility issues arise when importing and using the library at the code layer. Specifically, samber/lo does not compile with the latest version.

Proposed Solution:

1.	Refactor FRP to be more modular, allowing it to be imported as a library in the code layer without additional setup issues.
2.	Update the dependency to the latest version of samber/lo and ensure compatibility with the refactored structure.

Benefits:

•	Streamlined integration of FRP in projects where it acts as a library.
•	Future-proofing against potential versioning issues in samber/lo.

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @Guiwoo on GitHub (Nov 30, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4568 ### Describe the feature request Feature Request: Use FRP as a Library and Update samber/lo Dependency English Summary Problem: Currently, the project uses samber/lo as a dependency, but with the release of newer versions, compatibility issues arise when importing and using the library at the code layer. Specifically, samber/lo does not compile with the latest version. Proposed Solution: 1. Refactor FRP to be more modular, allowing it to be imported as a library in the code layer without additional setup issues. 2. Update the dependency to the latest version of samber/lo and ensure compatibility with the refactored structure. Benefits: • Streamlined integration of FRP in projects where it acts as a library. • Future-proofing against potential versioning issues in samber/lo. ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror closed this issue

2026-05-05 14:19:12 -06:00

Rows
Columns

[GH-ISSUE #4568] [Feature Request] Samber lo version up #3611

Describe the feature request

Describe alternatives you've considered

Affected area