Separate npm build of API catalog from gradle
Open
Nobody has claimed this yet.
Priority: High
size/M
technical excellence
V3
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Is your feature request related to a problem? Please describe.
For me as a developer, it takes very long to build the project. It seems that the most problematic part is in UI which is usually not changing so it should not be rebuilt each time.
Describe the solution you'd like
I would like to limit the amount of time it takes to build the project. One solution could be to take out npm projects, publish is separately, and download the result to gradle projects when needed.
Describe alternatives you've considered
Improve current monorepo to run faster and more stable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.