-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: use Bazel from npm #14170
build: use Bazel from npm #14170
Changes from all commits
8603132
63b39a2
bc5d280
396f3d1
ee1a093
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,12 +20,14 @@ | |
], | ||
"scripts": { | ||
"admin": "node ./bin/devkit-admin", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: would be nice to have There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Having the script proper is better I feel. It makes it pretty obvious that it's the right way of using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It comes with npm. If you’re only using yarn you should be able to just do ‘yarn bazel’ There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah you can |
||
"bazel:format": "find . -type f \\( -name \"*.bzl\" -or -name WORKSPACE -or -name BUILD -or -name BUILD.bazel \\) ! -path \"*/node_modules/*\" | xargs buildifier -v --warnings=attr-cfg,attr-license,attr-non-empty,attr-output-default,attr-single-file,constant-glob,ctx-args,depset-iteration,depset-union,dict-concatenation,duplicated-name,filetype,git-repository,http-archive,integer-division,load,load-on-top,native-build,native-package,output-group,package-name,package-on-top,positional-args,redefined-variable,repository-name,same-origin-load,string-iteration,unused-variable", | ||
"bazel:lint": "yarn bazel:format --lint=warn", | ||
"bazel:lint-fix": "yarn bazel:format --lint=fix", | ||
"bazel:test": "bazel test //...", | ||
"build": "npm run admin -- build", | ||
"build-tsc": "tsc -p tsconfig.json", | ||
"fix": "npm run admin -- lint --fix", | ||
"lint": "npm run admin -- lint", | ||
"prebuildifier": "bazel build --noshow_progress @com_github_bazelbuild_buildtools//buildifier", | ||
"buildifier": "find . -type f \\( -name BUILD -or -name BUILD.bazel \\) ! -path \"*/node_modules/*\" | xargs $(bazel info bazel-bin)/external/com_github_bazelbuild_buildtools/buildifier/buildifier", | ||
"templates": "node ./bin/devkit-admin templates", | ||
"test": "node ./bin/devkit-admin test", | ||
"test-large": "node ./bin/devkit-admin test --large --spec-reporter", | ||
|
@@ -79,6 +81,9 @@ | |
"devDependencies": { | ||
"@angular/compiler": "^8.0.0-beta.12", | ||
"@angular/compiler-cli": "^8.0.0-beta.12", | ||
"@bazel/bazel": "0.24.1", | ||
"@bazel/buildifier": "^0.22.0", | ||
"@bazel/jasmine": "~0.26.0", | ||
"@bazel/karma": "~0.26.0", | ||
"@bazel/typescript": "~0.26.0", | ||
"@ngtools/json-schema": "^1.1.0", | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this needed? We use
puppeteer
for our e2e tests so I didn't expect it to be necessary.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sadly headless chrome still requires dynamic linked dependency on libx11 which is pretty lame. We should raise with the Chrome team.