build-tool

Describe the feature you'd like to request

Show original CLI colors in the output.

Describe the solution you'd like

I would like to be able to have a --colors flag when running turbo to enable colors of the CLI output, including the output from the sub packages/apps. `tur

Currently, when using explicit cache a single cache image can be specified to read from. It could be useful to have a priority-ordered list of images to check for cache hits. @mattste provided this use case:

Use Case

I'm attempting to do pull request previews where each pull request has its own Docker image. For pull requests that update a dependency (such as a package.json or mix.lock),

I'm trying to create a wrapper for Task in Node.js. I'd like to report the time each task takes. However, the task variables show up as:

task: dynamic variable: 'if [ -f meta/main.yml ]; then yq e '.galaxy_info.role_name' meta/main.yml; else jq -r '.name' package.json | sed 's/.*\///'; fi' result: 'androidstudio'

They SHOULD show up as:

task: dynamic variable:  [common:update-a

steps

Using Scala 2.12.14 + SBT 1.5.x
Just include this import in your source

import java.time.temporal.ChronoUnit.MILLIS.{between => millisBetween}

problem

java.lang.NullPointerException
	at xsbt.Dependency$DependencyTraverser.lookupImported$1(Dependency.scala:394)
	at xsbt.Dependency$DependencyTraverser.$anonfun$traverse$1(Dependency.scala:396)
	at xsbt.Dependency$De

Just came across one of our client projects, which uses their own npm registry instead of the official one. By making it configurable via cli-flag like --registry https://my-registry.com we could support that use case.

I'm wondering if this is how we can make our npm plugin testable too! We could spin up a fake registry since we only ever download the tarball and use the --registry flag in

right now the image-loader middleware only supports the formats ICO, JPEG, PNG, GIF, SVG and WEBP.

It would be very useful to also add the new AVIF format, that is already being used on the web and that is quickly gaining popularity and browser supports

Currently when calling the MSBuild alias with an MSBuildSettings, we need to set the target using the WithTarget extension method.

MSBuild("./my-app.sln", new MSBuildSettings
{
    Configuration = "Release",
    ToolVersion = MSBuildToolVersion.VS2019,
}.WithTarget("Build")); // <<<###

It would be nice if we could use a property, with a string, which would make it more na

hello, i just found a text mentioning a basePxFontSize configuration which is not documented anywhere inside the doc. This is really useful to use inside custom transforms and it should be documented.

@rjrudin correctly points out in pantsbuild/pants#14684 that it's confusing why the help for sources for the python_sources target mentions .ext. Instead it really should mention .py.

This happens because we reuse the same help for every MultipleSourcesField. To fix, we need to have subclasses start setting more information. Two approaches:

1. Define a