chore: fix broken and redirecting links in docs

Update all outdated links in README.md and docs/ that pointed to old
/rules/ and /rulesets/ URL patterns or HTTP redirects:

- docs.aspect.build/rules/* and /rulesets/* → new /bazel/ path structure
- docs.aspect.build/workflows → aspect-workflows/get-started/overview
- docs.aspect.build/rules → docs.aspect.build/
- github.com/bazelbuild/rules_nodejs → github.com/bazel-contrib/rules_nodejs
- http://typescriptlang.org → https://www.typescriptlang.org
- https://cypress.io → https://www.cypress.io
- jq rule link removed (rule no longer exists in bazel_lib)
- rules_jest troubleshooting link removed (page no longer exists)

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

Author: kapunahelewong

README.md

@@ -18,22 +18,22 @@ The fastest way to try this in an empty project is to click the green "Use this
 
 rules_js is just a part Aspect's monorepo developer platform:
 
--   [Aspect Workflows](https://docs.aspect.build/workflows) delivers on Bazel's promises of speed and cost-savings.
+-   [Aspect Workflows](https://docs.aspect.build/aspect-workflows/get-started/overview) delivers on Bazel's promises of speed and cost-savings.
     It provides Continuous Integration and Delivery, including Remote Cache and Remote Build Execution (RBE).
     Best of all, it includes all the expertise that you expect from the team at Aspect!
 -   _Need help?_
     -   Best-effort community support is available on the #javascript channel on [Bazel Slack](https://slack.bazel.build/)
     -   Commercial support as a Slack Connect channel is offered by https://aspect.build/services.
--   See [Aspect's Bazel rules](https://docs.aspect.build/rules), especially those built for rules_js:
-    -   [rules_ts](https://github.com/aspect-build/rules_ts) - Bazel rules for [TypeScript](http://typescriptlang.org)
+-   See [Aspect's Bazel rules](https://docs.aspect.build/), especially those built for rules_js:
+    -   [rules_ts](https://github.com/aspect-build/rules_ts) - Bazel rules for [TypeScript](https://www.typescriptlang.org)
     -   [rules_swc](https://github.com/aspect-build/rules_swc) - Bazel rules for [swc](https://swc.rs)
     -   [rules_jest](https://github.com/aspect-build/rules_jest) - Bazel rules to run tests using [Jest](https://jestjs.io)
     -   [rules_esbuild](https://github.com/aspect-build/rules_esbuild) - Bazel rules for [esbuild](https://esbuild.github.io) JS bundler
     -   [rules_webpack](https://github.com/aspect-build/rules_webpack) - Bazel rules for [Webpack](https://webpack.js.org)
     -   [rules_rollup](https://github.com/aspect-build/rules_rollup) - Bazel rules for [Rollup](https://rollupjs.org) - a JavaScript bundler
     -   [rules_jasmine](https://github.com/aspect-build/rules_jasmine) - Bazel rules to run tests using [Jasmine](https://jasmine.github.io/)
     -   [rules_terser](https://github.com/aspect-build/rules_terser) - Bazel rules for [Terser](https://terser.org) - a JavaScript minifier
-    -   [rules_cypress](https://github.com/aspect-build/rules_cypress) - Bazel rules to run tests using [Cypress](https://cypress.io)
+    -   [rules_cypress](https://github.com/aspect-build/rules_cypress) - Bazel rules to run tests using [Cypress](https://www.cypress.io)
     -   [rules_lint](https://github.com/aspect-build/rules_lint) includes [eslint support](https://registry.bazel.build/docs/aspect_rules_lint#lint-eslint-bzl).
 
 ## Known issues
@@ -70,10 +70,10 @@ Larger examples can be found in our [bazel-examples](https://github.com/aspect-b
 ## Relationship to rules_nodejs
 
 rules_js is an alternative to the `build_bazel_rules_nodejs` Bazel module and
-accompanying npm packages hosted in https://github.com/bazelbuild/rules_nodejs,
+accompanying npm packages hosted in https://github.com/bazel-contrib/rules_nodejs,
 which is now unmaintained. All users are recommended to use rules_js instead.
 
-rules_js replaces some parts of [bazelbuild/rules_nodejs](http://github.com/bazelbuild/rules_nodejs) and re-uses other parts:
+rules_js replaces some parts of [bazelbuild/rules_nodejs](https://github.com/bazel-contrib/rules_nodejs) and re-uses other parts:
 
 | Layer                           | Legacy                        | Modern                  |
 | ------------------------------- | ----------------------------- | ----------------------- |

docs/troubleshooting.md

@@ -199,4 +199,4 @@ npm.npm_exclude_package_contents(
 
 #### Jest
 
-See [rules_jest](https://github.com/aspect-build/rules_jest) specific [troubleshooting](https://docs.aspect.build/rulesets/aspect_rules_jest/docs/troubleshooting#performance).
+See [rules_jest](https://github.com/aspect-build/rules_jest) for troubleshooting.

e2e/pnpm_lockfiles/v101/snapshots/is-odd-v0_resolved.json

@@ -54,7 +54,7 @@ The following environment variables are made available to the Node.js runtime ba
 The following environment variables are made available to the Node.js runtime based the runtime environment:
 
 * JS_BINARY__NODE_BINARY: the Node.js binary path run by the `js_binary` target
-* JS_BINARY__NPM_BINARY: the npm binary path; this is available when [`include_npm`](https://docs.aspect.build/rules/aspect_rules_js/docs/js_binary#include_npm) is `True` on the `js_binary` target
+* JS_BINARY__NPM_BINARY: the npm binary path; this is available when [`include_npm`](https://docs.aspect.build/bazel/javascript/aspect_rules_js/js_defs#include_npm) is `True` on the `js_binary` target
 * JS_BINARY__NODE_WRAPPER: the Node.js wrapper script used to run Node.js which is available as `node` on the `PATH` at runtime
 * JS_BINARY__RUNFILES: the absolute path to the Bazel runfiles directory
 * JS_BINARY__EXECROOT: the absolute path to the root of the execution root for the action; if in the sandbox, this path absolute path to the root of the execution root within the sandbox

e2e/pnpm_lockfiles/v101/snapshots/is-odd_resolved.json

@@ -83,7 +83,7 @@ Expected to find source file {file_basename} in '{this_package}', but instead it
 All source and data files that are not in the Bazel output tree must be in the same package as the
 target so that they can be copied to the output tree in an action.
 
-See https://docs.aspect.build/rules/aspect_rules_js/docs/#javascript for more context on why this is required.
+See https://docs.aspect.build/bazel/javascript/rules_js for more context on why this is required.
 
 Either move {file_basename} to '{this_package}', or add a 'js_library'
 target in {file_basename}'s package and add that target to the deps of {this_target}: