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.

Sign up for GitHub

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

Jump to bottom

Flatten NestJS to individual mono packages/service instead of being a fat package with multiple targets. #1779

Open
fuxingloh opened this issue Sep 23, 2022 · 1 comment
Open

Flatten NestJS to individual mono packages/service instead of being a fat package with multiple targets. #1779

fuxingloh opened this issue Sep 23, 2022 · 1 comment
Labels
area/apps area/packages area/workflow kind/feature New feature request triage/accepted Triage has been accepted

Comments

@fuxingloh
Copy link
Contributor

What would you like to be added:

With #1777 #1778 completed, we can move NestJS from a monolithic one giant package project (nest-apps) into a monorepo with multiple package projects with their own package.json and scripts. Further, we can take advantage of turbo prune to prune workspaces when building their relevant docker image.

Why is this needed:

/triage accepted
/area workflow packages
@fuxingloh fuxingloh added the kind/feature New feature request label Sep 23, 2022
@fuxingloh
Copy link
Contributor Author

/area apps

@fuxingloh fuxingloh mentioned this issue Sep 23, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/apps area/packages area/workflow kind/feature New feature request triage/accepted Triage has been accepted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fuxingloh @jellyfishsdk-bot