search

bazelbuild / examples

Examples for Bazel
http://bazel.build
Apache License 2.0
800 stars 497 forks source link

chore: replace an eslint_test with rules_lint #373

Closed alexeagle closed 7 months ago

alexeagle commented 7 months ago

Demo: uncomment the debugger line in next.js/pages/index.tsx, then:

~/Projects/examples/frontend/next.js$ npm run lint

> lint
> bazel build --config=lint //next.js/pages:all

INFO: Analyzed 9 targets (0 packages loaded, 0 targets configured).
ERROR: /home/alexeagle/Projects/examples/frontend/next.js/pages/BUILD.bazel:13:11: ESLint next.js/pages/ESLint.pages.aspect_rules_lint.report failed: (Exit 1): bash failed: error executing ESLint command (from target //next.js/pages:pages) /bin/bash -c 'bazel-out/k8-opt-exec-ST-13d3ddad9198/bin/next.js/eslint.sh $@ && touch bazel-out/k8-fastbuild/bin/next.js/pages/ESLint.pages.aspect_rules_lint.report' '' --no-eslintrc --config ... (remaining 5 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
Pages directory cannot be found at /tmp/bazel-working-directory/_main/bazel-out/k8-fastbuild/bin/pages or /tmp/bazel-working-directory/_main/bazel-out/k8-fastbuild/bin/src/pages. If using a custom path, please configure with the `no-html-link-for-pages` rule in your eslint config file.
next.js/pages/index.tsx:9:1: Unexpected 'debugger' statement  [error from no-debugger]

INFO: Found 9 targets...
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 1.236s, Critical Path: 1.09s
INFO: 2 processes: 2 internal.
ERROR: Build did NOT complete successfully
INFO: Build Event Protocol files produced successfully.