docs: update master links to stable branch

docs/TypeScript.md

@@ -781,7 +781,7 @@ observe these problems which require workarounds:
    `error TS6305: Output file '/path/to/execroot/a.d.ts' has not been built from source file '/path/to/execroot/a.ts'.`
    As a workaround, you can give the Windows "fastbuild" output directory as the `outDir` in your tsconfig file.
    On other platforms, the value isn't read so it does no harm.
-   See https://github.com/bazelbuild/rules_nodejs/tree/master/packages/typescript/test/ts_project as an example.
+   See https://github.com/bazelbuild/rules_nodejs/tree/stable/packages/typescript/test/ts_project as an example.
    We hope this will be fixed in a future release of TypeScript;
    follow https://github.com/microsoft/TypeScript/issues/37378
 

docs/examples.md

@@ -13,15 +13,15 @@ See Alex's post [Angular ❤️ Bazel update](https://dev.to/bazel/angular-bazel
 
 **Architect**: The first approach is the simplest: use Architect (aka. Angular CLI Builders). This is the build tool inside of Angular CLI, so your existing application will continue to work the same way. However, it has the worst performance because the level of incrementality is only as fine as how many libs your application is composed from.
 
-Example: [examples/angular_bazel_architect](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/angular_bazel_architect)
+Example: [examples/angular_bazel_architect](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular_bazel_architect)
 
 **Google**: This toolchain is what we originally advertised as "Angular, Bazel and CLI" (ABC). It is based on Google's internal toolchain for building Angular, and has good performance characteristics. However it is harder to migrate to, because it doesn't have good compatibility for existing applications.
 
-The example has its own guide: [examples/angular](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/angular)
+The example has its own guide: [examples/angular](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular)
 
 **View Engine**: If you're stuck on the older Angular compiler/runtime before Ivy, called View Engine, then your options are more limited. We don't support Angular 9 + View Engine + Bazel.
 
-Example: [examples/angular_view_engine](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/angular_view_engine)
+Example: [examples/angular_view_engine](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular_view_engine)
 
 ## React
 
@@ -36,7 +36,7 @@ a bigger full-stack Bazel build, this might be the final step in the migration.
 However it will run `react-scripts` as a single Bazel action, which means that you gain no incrementality benefit.
 So we expect for most applications this is just a first step.
 
-The [create-react-app example](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/create-react-app)
+The [create-react-app example](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/create-react-app)
 shows how this will look. We suggest reading the README in that example, and also look at the commit history to that
 directory as an illustration of how we started from create-react-app and added Bazel bits.
 
@@ -51,7 +51,7 @@ for you by maintainers of a project like create-react-app, who have a very high
 maintenance and support burden falls on them. However you'll need to understand both the tools as well as Bazel to
 successfully build your own toolchain.
 
-There is a basic example at [examples/react_webpack](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/react_webpack) but it needs a lot more work to show everything that is possible!
+There is a basic example at [examples/react_webpack](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/react_webpack) but it needs a lot more work to show everything that is possible!
 
 ## Vue
 
@@ -65,15 +65,15 @@ None yet, please file an issue if you need this.
 
 ## Jest
 
-There is a dedicated example for Jest: [examples/jest](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/jest)
+There is a dedicated example for Jest: [examples/jest](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/jest)
 
 ## Cypress
 
 We have done some early work to run Cypress under Bazel. Follow https://github.com/bazelbuild/rules_nodejs/issues/1904 for an example.
 
 ## Mocha
 
-Example at [examples/webapp](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/webapp) has a simple `mocha_test`
+Example at [examples/webapp](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/webapp) has a simple `mocha_test`
 
 ## Karma and Protractor
 
@@ -83,46 +83,46 @@ See Protractor usage in [examples/app](https://github.com/bazelbuild/rules_nodej
 
 ## Webpack
 
-See [examples/react_webpack](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/react_webpack)
+See [examples/react_webpack](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/react_webpack)
 
 ## Rollup
 
-The example at [examples/webapp](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/webapp) uses Rollup, and produces an app with ES5 and ES2015 variants ("differential loading") that gives faster loading in modern browsers without dropping support for legacy ones.
+The example at [examples/webapp](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/webapp) uses Rollup, and produces an app with ES5 and ES2015 variants ("differential loading") that gives faster loading in modern browsers without dropping support for legacy ones.
 
 ## Parcel
 
-The example in [examples/parcel](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/parcel) shows how to write a custom rule, it happens to use the parcel binary to build. It's a very minimal example but might be enough to get you started. 
+The example in [examples/parcel](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/parcel) shows how to write a custom rule, it happens to use the parcel binary to build. It's a very minimal example but might be enough to get you started. 
 
 # Language tooling
 
 ## LESS, Sass, Stylus
 
-See styles directory inside the [examples/app](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/app/styles) example.
+See styles directory inside the [examples/app](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/app/styles) example.
 
 ## TypeScript
 
-Most of the examples show TypeScript usage. Also look in [packages/typescript/test](https://github.com/bazelbuild/rules_nodejs/tree/master/packages/typescript/test) for lots of handling of edge cases.
+Most of the examples show TypeScript usage. Also look in [packages/typescript/test](https://github.com/bazelbuild/rules_nodejs/tree/stable/packages/typescript/test) for lots of handling of edge cases.
 
 ## Kotlin
 
 The Kotlin language can compile to JS. The result has a very large stdlib JS payload, so we don't recommend this for most uses.
 
-Example at [examples/kotlin](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/kotlin)
+Example at [examples/kotlin](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/kotlin)
 
 ## Google Closure Compiler
 
 [rules_closure](https://github.com/bazelbuild/rules_closure) is a whole-cloth approach to using Bazel if you're fully bought-into the Closure ecosystem.
 
-[examples/closure](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/closure) shows a very simple way to call the closure compiler without jumping into that ecosystem.
+[examples/closure](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/closure) shows a very simple way to call the closure compiler without jumping into that ecosystem.
 
 ## Protocol Buffers and gRPC
 
 Note: this is considered a "labs" feature in rules_nodejs, so support and stability are not great. gRPC is still a WIP.
 
-See [examples/protocol_buffers](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/protocol_buffers)
+See [examples/protocol_buffers](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/protocol_buffers)
 
 # Bazel-specific
 
 ## Bazel Persistent Workers
 
-If you want to speed up Bazel by keeping some tools running warm in the background as daemons, there's a good readme in the [examples/worker](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/worker)
+If you want to speed up Bazel by keeping some tools running warm in the background as daemons, there's a good readme in the [examples/worker](https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/worker)

docs/repositories.md

@@ -54,7 +54,7 @@ Commonly used ones are:
 - Sometimes you need a UMD bundle, but a package doesn't ship one. For example, the `ts_devserver` rule depends on third-party libraries having a named UMD entry point. The `@npm//foo:foo__umd` target will automatically run Browserify to convert the package's `main` entry into UMD.
 - DEPRECATED: A helper to install npm packages into their own Bazel repository: `@npm//:install_bazel_dependencies.bzl` provides a `install_bazel_dependencies` function. Some npm packages ship custom bazel rules, for example, the `@angular/bazel` package provides rules which you should load from `@npm_angular_bazel//:index.bzl`. However this causes the build to always fetch npm packages even when not needed, so we plan to remove this in a future release.
 
-> One convenient (maybe also confusing) way to understand what BUILD files are generated is to look at our integration test at https://github.com/bazelbuild/rules_nodejs/tree/master/internal/npm_install/test/golden - this directory looks similar to the content of an `@npm` repository.
+> One convenient (maybe also confusing) way to understand what BUILD files are generated is to look at our integration test at https://github.com/bazelbuild/rules_nodejs/tree/stable/internal/npm_install/test/golden - this directory looks similar to the content of an `@npm` repository.
 
 ### Generated macros for npm packages with `bin` entries
 

examples/angular/src/index.html

@@ -80,7 +80,7 @@
             mat-button=""
             tabindex="0"
             aria-disabled="false"
-            href="https://github.com/bazelbuild/rules_nodejs/tree/master/examples/angular"
+            href="https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular"
             ><span class="mat-button-wrapper">Example</span>
             <div class="mat-button-ripple mat-ripple" matripple=""></div>
             <div class="mat-button-focus-overlay"></div

packages/typescript/internal/ts_project.bzl

@@ -318,7 +318,7 @@ def ts_project_macro(
        `error TS6305: Output file '/path/to/execroot/a.d.ts' has not been built from source file '/path/to/execroot/a.ts'.`
        As a workaround, you can give the Windows "fastbuild" output directory as the `outDir` in your tsconfig file.
        On other platforms, the value isn't read so it does no harm.
-       See https://github.com/bazelbuild/rules_nodejs/tree/master/packages/typescript/test/ts_project as an example.
+       See https://github.com/bazelbuild/rules_nodejs/tree/stable/packages/typescript/test/ts_project as an example.
        We hope this will be fixed in a future release of TypeScript;
        follow https://github.com/microsoft/TypeScript/issues/37378
 

packages/worker/README.md

@@ -10,7 +10,7 @@ Read `index.d.ts` for the worker API. Essentially you call `runWorkerLoop` passi
 
 See the [worker example] for a full example with comments.
 
-[worker example]: https://github.com/bazelbuild/rules_nodejs/tree/master/examples/worker
+[worker example]: https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/worker
 
 ## Restrictions on programs that run as a worker