shorter links to rules_nodejs bugs

README.md

@@ -11,7 +11,7 @@ we use a Bazel-idiomatic approach to managing the third-party dependencies.
 
 Features include:
 
--   Only downloads packages from npm which are needed for the requested targets to be built/tested. (https://github.com/bazelbuild/rules_nodejs/issues/2121)
+-   Only downloads packages from npm which are needed for the requested targets to be built/tested. [#2121](https://github.com/bazelbuild/rules_nodejs/issues/2121)
 -   Bazel downloader caches the npm package files,
     so no fetches are required when the repository rule is cache-busted.
 -   Always represents npm packages as directories (TreeArtifact's in Bazel terminology) so there are few inputs to Bazel actions,
@@ -23,11 +23,11 @@ See the [design doc](https://hackmd.io/gu2Nj0TKS068LKAf8KanuA)
 In addition, as a clean rewrite many of the bugs in rules_nodejs are naturally resolved:
 
 -   Drop four years of accumulated complexity.
--   No Bash dependency on Windows, (https://github.com/bazelbuild/rules_nodejs/issues/1102)
--   nodejs_binary can be used as the `tool` in a genrule (https://github.com/bazelbuild/rules_nodejs/issues/1553, https://github.com/bazelbuild/rules_nodejs/issues/2600)
+-   No Bash dependency on Windows, [#1102](https://github.com/bazelbuild/rules_nodejs/issues/1102)
+-   nodejs_binary can be used as the `tool` in a genrule [#1553](https://github.com/bazelbuild/rules_nodejs/issues/1553), [#2600](https://github.com/bazelbuild/rules_nodejs/issues/2600)
 -   Repository layout matches the distribution so you can trivially patch or point to sources.
 -   We use gazelle to generate bzl_library targets so users can always generate documentation
-    for rules that reference these. (https://github.com/bazelbuild/rules_nodejs/issues/2874)
+    for rules that reference these. [#2874](https://github.com/bazelbuild/rules_nodejs/issues/2874)
 
 ## Installation