build-tool

What version of Turborepo are you using?

1.2.11

What package manager are you using / does the bug impact?

pnpm

What operating system are you using?

Mac

Describe the Bug

In the past JSON5 support was added to turbo.json but adding // comment now breaks with:

error unmarshalling invalid character '/' looking for beginning of object key string
ERROR  turbo.json: in

Request to create a syntax highlight package for Atom IDE https://atom.io/

Related to #1203 #359

source: https://insights.stackoverflow.com/survey/2021#most-popular-technologies-new-collab-tools

When integrating with other tools (like vscode extension, or when trying to script exporting tasks to github actions) we really want to avoid having to parse the free-form output, especially as this will likely change and break integration, even between minor versions.

If we would output as JSON, we can make the parsing far more reliable and less likely to break between versions, especially as

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

steps

I have reproduced the bug with both sbt 1.6.2 and 1.6.0, but no problem with sbt 1.5.8.

To reproduce, just take any SBT project using SBT 1.6 and try to compile with Scala 2.12.4, eg.

sbt new scala/scala-seed.g8
# cd into directory and change Scala version to 2.12.4
sbt compile

Note that the issue does not show up with Scala versions 2.12.2, 2.12.3, nor 2.12.5.

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

One of the consumers of our system uses curly braces for content replacement in strings.

Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.

I have tried a number of ways to escape the braces with no luck

Other languages and templating systems seem to use the concept of using double curly b

Describe the bug

Latest docs suggest using "$regex$DEPRECATED:\\s*" for filtering deprecation log messages.

Having this configuration in the pants.toml file:

[GLOBAL]
ignore_warnings = ["$regex$DEPRECATED:\\s*"]

Results in warning messages printed:

10:28:38.

Would it be possible to support multiple files as input / output using the CLI?

PostCSS and ESbuild allow to use a glob pattern for the input and have arguments to set the output directory and extension.

Examples:

• postcss src/**/*.css --base src --dir dist/css --ext .min.css
• esbuild src/**/*.js --bundle --outdir=dist/JS --out-extension:.js=.min.js

A similar solution would be ve