You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal of this ticket is to find one real-world Typescript project and port it to Mill, similar to what we did with Mockito (as a comparison to Gradle), Netty (as a comparison to Maven), and Arrow (as a comparison for Gradle Kotlin).
The project should be an existing medium-sized multi-module Typescript codebase with between 10-50 submodules
Almost all code should compile and all tests should pass using Mill.
There should be minimal code that does not compile/test in the Mill build, and each such part of the codebase must be justified as to why it cannot be supported in Mill
The application code should be left entirely in place; the only change should be the addition of a Mill build
The end result should be a performance and functionality comparison of building and testing the project using Mill v.s. the existing build tool
The text was updated successfully, but these errors were encountered:
lihaoyi
changed the title
Port a real-world Typescript project to the Mill build tool for comparison purposes
Port a real-world Typescript project to the Mill build tool for comparison purposes (1000USD Bounty)
Jan 29, 2025
From the maintainer Li Haoyi: I'm putting a 1000USD bounty on this issue, payable by bank transfer on a merged PR implementing this.
Follow up of #3927.
The goal of this ticket is to find one real-world Typescript project and port it to Mill, similar to what we did with Mockito (as a comparison to Gradle), Netty (as a comparison to Maven), and Arrow (as a comparison for Gradle Kotlin).
The end result should be a performance and functionality comparison of building and testing the project using Mill v.s. the existing build tool
The text was updated successfully, but these errors were encountered: