build-tool

We don't yet have good examples on how to use build args and the different things the user might be able to do with them. This is the only page that goes into a bit more detail https://docs.earthly.dev/docs/guides/build-args.

Ideally:

• The tutorial includes a step that shows how they are used (including code)
• There is an isolated example just for build args

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

For the sake of completeness, the Task runner in verbose with (i.e. task -vvvvv) should report when a task is complete and starts.

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.

Running e.g. ./pants help tailor shows:

help tailor

`tailor` goal options
---------------------

Auto-generate BUILD file targets for new source files.

Config section: [tailor]

None available.

... which doesn't indicate that there are any advanced options. There are, in this case.

If a goal/subsystem has advanced options, the output of help should tell users th

This issue is tracking the documentation that has to be updated.

• Document new platform commands
• Update the section dedicated to page <title> and tell about [Browser.documen