Formerly, developers were directed to install Go and a specific
library dependency on their workstation. We can pull this all into bazel
using bazelbuild/rules_go and bazelbuild/bazel-gazelle.
Now, instead of running a script from a specific directory, the dev
server can be started with a simple "bazel run" command. Or, continue
using the script, which automatically releases the bazel lock before
starting the server.
Change-Id: I9dbda32a8c8698b3f43d02b2133d3cecbffaf1c3
Some platforms either don't have bash installed as /bin/bash. Use
the environment to find it in the PATH.
Change-Id: Ie1a6d64146927c83af07d0e2ca7f573c7504f8ef
Makes test components (iron-test-helpers, etc) available for tests at
http://localhost:8081/elements/foo/bar_test.html
Also, once server was started and bower_components folder was rebuilt,
enables wct cli:
wct -l chrome -p ./polygerrit-ui/app/elements/foo_test.html
Change-Id: I743d07ee4ba158bf57e1e1214f67f98ba22beb2b
- include 'web-component-tester' bower dependency as test-dependency
- remove special handling for serving folder 'bower_components'
- add support for passing parameters from 'run-server.sh' to 'server.go'
Change-Id: Ia74b3013e07b6304a4df568b081254909749efc5
Build and extract bower_components to the local directory from
buck-out. This is easier than modifying server.go to serve from a zip
file.
Running `bower install` before server.go was the last remaining usage
of bower.json, so we can just remove it.
Change-Id: Ic4717a3a1652ad08e1cef871c0a207c2c382aa35