build-tool

steps

Use the following project/build.properties:

sbt.version=1.5.4

and the following build.sbt:

inThisBuild(Def.settings(
  crossScalaVersions := Seq("2.12.3", "2.10.6"),
  scalaVersion := "2.12.3",

  crossSbtVersions := Seq("1.0.2", "0.13.16"),
))

lazy val `sbt-platform-deps` = project.in(file("."))
  .enablePlugins(SbtPlugin)

Launch sbt

p

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

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

The MSBuildSettings extension UseToolVersion expects a valid value from the MSBuildToolVersion enumeration.

public static MSBuildSettings UseToolVersion(this MSBuildSettings settings, MSBuil

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.

debootstrap.sh replaces extraargs or another line in the environment where it finds 'console=' before the line that starts with console=

Suggested the following fix:

--- a/lib/debootstrap.sh
+++ b/lib/debootstrap.sh
@@ -626,7 +626,7 @@ prepare_partitions()
 	# if we have a headless device, set console to DEFAULT_CONSOLE
 	if [[ -n $DEFAULT_CONSOLE && -f $SDCARD/boot/armbianE

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

Right now it fails in all sorts of subtle ways relating to failures to resolve requirements and picking weird interpreters (e.g., due to the issue explained in pantsbuild/pex#957).

It hypothetically possible to build lambdas on MacOS if all transitive requirements have prebuilt linux wheels, but that is too narrow a case to support, and it's subtle and tricky to get ri