This is a good first PR!

We should add some tests to cover #7036. They should cover both JavaScript and TypeScript support.

They can probably be added to test/fixtures.

TestCafe runs on Windows, MacOS, and Linux. It supports multiple desktop (Chrome, Firefox, IE11, Edge, Safari), mobile, remote and cloud browsers (UI or headless). TestCafe is free to use under the MIT license.

https://devexpress.github.io/testcafe/
https://github.com/devexpress/testcafe

Can you please add spec for WRF and CFS ?

WRF link - https://github.com/wrf-model/WRF.git
CFS link - http://cfs.ncep.noaa.gov/cfsv2/cfsv2_source.tar.gz

Will appreciate your efforts in this regard :)

Right now, a target name can contain space, comma, /, etc, so it would be a good idea to limit it to alphanumeric + - and _

For example:

diff --git a/BUILD b/BUILD
index 0ad0a46..c71bab2 100644
--- a/BUILD
+++ b/BUILD
@@ -52,3 +52,6 @@ files(
   name = 'pants_pex',
   source = 'pants.pex',
 )
+
+target(
+  name = '123/456')


$ ./pants list :
//:123/456

In the Tutorial, under Adding A Runnable Script, the results are the same as the previous section, Adding Python Source Files, except for the timestamp and the runtime of 1 element

It is better to have socket file as server entry point. Especially in a multi-user server, it makes users independent work locally.

Faq page will be added to https://flubucore.dotnetcore.xyz/

If anyone have a proposition about what to add to FAQ page please leave a comment in this issue.

The documentation for the 'cflags' feature in the latest Boost Build docs says:

"For cflags that is both the C and C++ compilers, for cxxflags that is the C++ compiler"

but this is not reflected in the common.handle-options rule, which has 'cflags' being set for the toolset's 'compile.c' rule rather than for the toolset's 'compile' rule, while the 'compileflags' feature, which is no longer d

Our user docs should have a page that lists and describes BLT's configuration options.

Right now, If I cd to an empty directory, and execute walk, this is what I see:

dir $ walk
dir $

No output. walk is doing the right thing, since the intended behavior of a dependency in a directory without a Walkfile is to assume that the dependency is a static file, or a noop dep.

However, in the above case, where I'm executing a root target that has no Walkfile,

Hi,

It's not something you can fix I think, but I think it's probably worth mentioning it on the documentation.

When installing Python 2 or 3 in Windows, the name of the executable is python.exe. When you use Python2 rules, it's looking for python2 and when Python3 it's looking for python3. Even if you can figure out it's Windows run - calling 'Python' is not enough because you don't k