-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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.
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
Move to turbo.json
#218
Move to turbo.json
#218
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/vercel/turbo-site/2taK9KreSB3WmYHxVuXd6ECLVXsx |
Pretty excited about this as this PR suggests Turborepo will support taking environment variables into account for the hashes. Also like having |
I agree! package.json is pretty hard to keep track of with all of that configuration. |
Superseded by #606 |
Split from #209 This lets any non-`#[turbo_tasks::value]` struct be debug-formatted properly when inside another `#[turbo_tasks::value]` struct. e.g. ```rust #[turbo_tasks::value] struct Value1 { value2: Value2, } #[derive(TraceRawVcs, Serialize, Debug, Deserialize, PartialEq, Eq) struct Value2 { value3: Value3Vc } #[turbo_tasks::value] struct Value3 { str: StringVc } ``` Prints: ```rust Value1 { value2: Value2 { value3: Value3Vc { node: TaskCell( TaskId { id: 58, }, 0, ), }, }, } ``` Replacing the `Debug` derive with `ValueDebugFormat` for `Value2` prints: ```rust Value1 { value2: Value2 { value3: Value3 { str: "hello!" }, }, } ```
Close #217