[Refactor/Chore] Introduce pnpm workspace #22031

Open
opened 2026-02-21 20:15:22 -05:00 by yindo · 1 comment
Owner

Originally created by @hyoban on GitHub (Feb 3, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactors or chores; if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Description

https://pnpm.io/workspaces

Our codebase has grown very large and lacks strict module boundaries, which is detrimental to maintainability and reusability. We can consider dividing it into modules: base config, basic components, state management, and network requests.

Of course, we hope this change won't cause too much diff (or maybe we need a good time) and won't break the existing build.

Maybe we can first use directories to organize the modules, ensuring there are no unnecessary dependencies between them.

Motivation

No response

Additional Context

No response

Originally created by @hyoban on GitHub (Feb 3, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for refactors or chores; if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :) - [x] Please do not modify this template :) and fill in all the required fields. ### Description https://pnpm.io/workspaces Our codebase has grown very large and lacks strict module boundaries, which is detrimental to maintainability and reusability. We can consider dividing it into modules: base config, basic components, state management, and network requests. Of course, we hope this change won't cause too much diff (or maybe we need a good time) and won't break the existing build. Maybe we can first use directories to organize the modules, ensuring there are no unnecessary dependencies between them. ### Motivation _No response_ ### Additional Context _No response_
yindo added the status: in discussion label 2026-02-21 20:15:22 -05:00
Author
Owner

@hyoban commented on GitHub (Feb 3, 2026):

FYI @jinghaihan

@hyoban commented on GitHub (Feb 3, 2026): FYI @jinghaihan
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#22031