Description of the problem / feature request:

The presence of a .bazelversion file that defines any non-matching version at the root of a directory structure prevents bazel from intepreting any commands in any subdirectory, including bazel version, help, info.

However, these are the commands needed to debug why .bazelversion is not satisfied, or to query non-build-related hel

It may be convenient to expose something to consumers that will make it easier to use Jest - something like the default babel options (presets, plugins, etc.) or a transform module (see something like https://github.com/ActuallyACat/jest-esm-transformer).

This makes using syntax like import/export much easier for folks who use this amazing library for bundling and Jest for tests.

Thank y

We have several errors/warnings that have a URL in the text of the message. After #5488 (thanks, @jmezac!) we'll have a structured way to represent this that will eventually (dotnet/project-system#6335) be used in the Visual Studio UI.

We should use that!

Likely candidates:

$ rg "fwlink|aka\.ms" -g *resx
src\Tasks\Resources\Strings.resx
683:    <

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Some of the repos that we import has ".go" in the file path. eg. https://github.com/nats-io/nats.go.

When using packr v2 to build packr parses the folder path as a file and reports error ".../nats.go" is a directory.

The issue is in findAllGoFiles in jam/parser/finder.go

I am happy to raise a PR if you like

Dune systematically buffers the output of commands so that their output is not mixed up during parallel builds. However, this is not ideal for interactive commands that require direct access to the terminal.

Currently, the only workaround is to run dune with -j 1 --no-buffer which is not ideal since it completely disables parallelism and also require a specific dune invocation.

Another ide

If I do the following in my build.earth file:

ENV ${CODE_SRC}=/go/src/<project>

protobuf:
    COPY --dir api ${CODE_SRC}/backend

Then running earth +protobuf results in the files being copied into /backend:

+protobuf | --> COPY [api] /backend

I have worked around this by specifying the full path in the copy command:

ENV ${CODE_SRC}=/go/src/<project>

pro