Replace Smusher and Swagger with redocly

.aspect/bazelrc/.gitignore

@@ -0,0 +1 @@
+user.bazelrc

.aspect/bazelrc/BUILD.bazel

@@ -0,0 +1,14 @@
+"Aspect bazelrc presets; see https://docs.aspect.build/guides/bazelrc"
+
+load("@aspect_bazel_lib//lib:bazelrc_presets.bzl", "write_aspect_bazelrc_presets")
+
+write_aspect_bazelrc_presets(
+    name = "update_aspect_bazelrc_presets",
+    presets = [
+        "convenience",
+        "correctness",
+        "debug",
+        "javascript",
+        "performance",
+    ],
+)

.aspect/bazelrc/convenience.bazelrc

@@ -0,0 +1,28 @@
+# Attempt to build & test every target whose prerequisites were successfully built.
+# Docs: https://bazel.build/docs/user-manual#keep-going
+build --keep_going
+
+# Output test errors to stderr so users don't have to `cat` or open test failure log files when test
+# fail. This makes the log noisier in exchange for reducing the time-to-feedback on test failures for
+# users.
+# Docs: https://bazel.build/docs/user-manual#test-output
+test --test_output=errors
+
+# Show the output files created by builds that requested more than one target. This helps users
+# locate the build outputs in more cases
+# Docs: https://bazel.build/docs/user-manual#show-result
+build --show_result=20
+
+# Bazel picks up host-OS-specific config lines from bazelrc files. For example, if the host OS is
+# Linux and you run bazel build, Bazel picks up lines starting with build:linux. Supported OS
+# identifiers are `linux`, `macos`, `windows`, `freebsd`, and `openbsd`. Enabling this flag is
+# equivalent to using `--config=linux` on Linux, `--config=windows` on Windows, etc.
+# Docs: https://bazel.build/reference/command-line-reference#flag--enable_platform_specific_config
+common --enable_platform_specific_config
+
+# Output a heap dump if an OOM is thrown during a Bazel invocation
+# (including OOMs due to `--experimental_oom_more_eagerly_threshold`).
+# The dump will be written to `<output_base>/<invocation_id>.heapdump.hprof`.
+# You may need to configure CI to capture this artifact and upload for later use.
+# Docs: https://bazel.build/reference/command-line-reference#flag--heap_dump_on_oom
+common --heap_dump_on_oom

.aspect/bazelrc/correctness.bazelrc

@@ -0,0 +1,64 @@
+# Do not upload locally executed action results to the remote cache.
+# This should be the default for local builds so local builds cannot poison the remote cache.
+# It should be flipped to `--remote_upload_local_results` on CI
+# by using `--bazelrc=.aspect/bazelrc/ci.bazelrc`.
+# Docs: https://bazel.build/reference/command-line-reference#flag--remote_upload_local_results
+build --noremote_upload_local_results
+
+# Don't allow network access for build actions in the sandbox.
+# Ensures that you don't accidentally make non-hermetic actions/tests which depend on remote
+# services.
+# Developers should tag targets with `tags=["requires-network"]` to opt-out of the enforcement.
+# Docs: https://bazel.build/reference/command-line-reference#flag--sandbox_default_allow_network
+build --sandbox_default_allow_network=false
+
+# Warn if a test's timeout is significantly longer than the test's actual execution time.
+# Bazel's default for test_timeout is medium (5 min), but most tests should instead be short (1 min).
+# While a test's timeout should be set such that it is not flaky, a test that has a highly
+# over-generous timeout can hide real problems that crop up unexpectedly.
+# For instance, a test that normally executes in a minute or two should not have a timeout of
+# ETERNAL or LONG as these are much, much too generous.
+# Docs: https://bazel.build/docs/user-manual#test-verbose-timeout-warnings
+test --test_verbose_timeout_warnings
+
+# Allow the Bazel server to check directory sources for changes. Ensures that the Bazel server
+# notices when a directory changes, if you have a directory listed in the srcs of some target.
+# Recommended when using
+# [copy_directory](https://github.com/bazel-contrib/bazel-lib/blob/main/docs/copy_directory.md) and
+# [rules_js](https://github.com/aspect-build/rules_js) since npm package are source directories
+# inputs to copy_directory actions.
+# Docs: https://bazel.build/reference/command-line-reference#flag--host_jvm_args
+startup --host_jvm_args=-DBAZEL_TRACK_SOURCE_DIRECTORIES=1
+
+# Allow exclusive tests to run in the sandbox. Fixes a bug where Bazel doesn't enable sandboxing for
+# tests with `tags=["exclusive"]`.
+# Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_exclusive_test_sandboxed
+test --incompatible_exclusive_test_sandboxed
+
+# Use a static value for `PATH` and does not inherit `LD_LIBRARY_PATH`. Doesn't let environment
+# variables like `PATH` sneak into the build, which can cause massive cache misses when they change.
+# Use `--action_env=ENV_VARIABLE` if you want to inherit specific environment variables from the
+# client, but note that doing so can prevent cross-user caching if a shared cache is used.
+# Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_strict_action_env
+build --incompatible_strict_action_env
+
+# Do not automatically create `__init__.py` files in the runfiles of Python targets. Fixes the wrong
+# default that comes from Google's internal monorepo by using `__init__.py` to delimit a Python
+# package. Precisely, when a `py_binary` or `py_test` target has `legacy_create_init` set to `auto (the
+# default), it is treated as false if and only if this flag is set. See
+# https://github.com/bazelbuild/bazel/issues/10076.
+# Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_default_to_explicit_init_py
+build --incompatible_default_to_explicit_init_py
+
+# Set default value of `allow_empty` to `False` in `glob()`. This prevents a common mistake when
+# attempting to use `glob()` to match files in a subdirectory that is opaque to the current package
+# because it contains a BUILD file. See https://github.com/bazelbuild/bazel/issues/8195.
+# Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_disallow_empty_glob
+common --incompatible_disallow_empty_glob
+
+# Always download coverage files for tests from the remote cache. By default, coverage files are not
+# downloaded on test result cache hits when --remote_download_minimal is enabled, making it impossible
+# to generate a full coverage report.
+# Docs: https://bazel.build/reference/command-line-reference#flag--experimental_fetch_all_coverage_outputs
+# detching remote cache results
+test --experimental_fetch_all_coverage_outputs

.aspect/bazelrc/debug.bazelrc

@@ -0,0 +1,19 @@
+############################################################
+# Use `bazel test --config=debug` to enable these settings #
+############################################################
+
+# Stream stdout/stderr output from each test in real-time.
+# Docs: https://bazel.build/docs/user-manual#test-output
+test:debug --test_output=streamed
+
+# Run one test at a time.
+# Docs: https://bazel.build/reference/command-line-reference#flag--test_strategy
+test:debug --test_strategy=exclusive
+
+# Prevent long running tests from timing out.
+# Docs: https://bazel.build/docs/user-manual#test-timeout
+test:debug --test_timeout=9999
+
+# Always run tests even if they have cached results.
+# Docs: https://bazel.build/docs/user-manual#cache-test-results
+test:debug --nocache_test_results

.aspect/bazelrc/javascript.bazelrc

@@ -0,0 +1,11 @@
+# Aspect recommended Bazel flags when using Aspect's JavaScript rules: https://github.com/aspect-build/rules_js
+# Docs for Node.js flags: https://nodejs.org/en/docs/guides/debugging-getting-started/#command-line-options
+
+# Support for debugging Node.js tests. Use bazel run with `--config=debug` to turn on the NodeJS
+# inspector agent. The node process will break before user code starts and wait for the debugger to
+# connect. Pass the --inspect-brk option to all tests which enables the node inspector agent. See
+# https://nodejs.org/de/docs/guides/debugging-getting-started/#command-line-options for more
+# details.
+# Docs: https://nodejs.org/en/docs/guides/debugging-getting-started/#command-line-options
+run:debug -- --node_options=--inspect-brk
+test:debug --test_env=NODE_OPTIONS=--inspect-brk

.aspect/bazelrc/performance.bazelrc

@@ -0,0 +1,19 @@
+# Directories used by sandboxed non-worker execution may be reused to avoid unnecessary setup costs.
+# Save time on Sandbox creation and deletion when many of the same kind of action run during the
+# build.
+# No longer experimental in Bazel 6: https://github.com/bazelbuild/bazel/commit/c1a95501a5611878e5cc43a3cc531f2b9e47835b
+# Docs: https://bazel.build/reference/command-line-reference#flag--reuse_sandbox_directories
+build --experimental_reuse_sandbox_directories
+
+# Avoid creating a runfiles tree for binaries or tests until it is needed.
+# Docs: https://bazel.build/reference/command-line-reference#flag--build_runfile_links
+# See https://github.com/bazelbuild/bazel/issues/6627
+#
+# This may break local workflows that `build` a binary target, then run the resulting program
+# outside of `bazel run`. In those cases, the script will need to call
+# `bazel build --build_runfile_links //my/binary:target` and then execute the resulting program.
+build --nobuild_runfile_links
+
+# Needed prior to Bazel 8; see
+# https://github.com/bazelbuild/bazel/issues/20577
+coverage --build_runfile_links

.bazeliskrc

@@ -1,2 +1,2 @@
 BAZELISK_BASE_URL=https://github.com/bazelbuild/bazel/releases/download
-USE_BAZEL_VERSION= 7.4.1
+USE_BAZEL_VERSION= 7.6.0

.bazelrc

@@ -1,74 +1,27 @@
-# Common Bazel settings for JavaScript/NodeJS workspaces
-# This rc file is automatically discovered when Bazel is run in this workspace,
-# see https://docs.bazel.build/versions/master/guide.html#bazelrc
-#
-# The full list of Bazel options: https://docs.bazel.build/versions/master/command-line-reference.html
 
-# Cache action outputs on disk so they persist across output_base and bazel shutdown (eg. changing branches)
-build --disk_cache=.cache/bazel-disk-cache
+# Import Aspect recommended Bazel convenience settings for all projects
+import %workspace%/.aspect/bazelrc/convenience.bazelrc
 
-# Specifies desired output mode for running tests.
-# Valid values are
-#   'summary' to output only test status summary
-#   'errors' to also print test logs for failed tests
-#   'all' to print logs for all tests
-#   'streamed' to output logs for all tests in real time
-#     (this will force tests to be executed locally one at a time regardless of --test_strategy value).
-test --test_output=errors
+# Import Aspect recommended Bazel correctness settings for all projects
+import %workspace%/.aspect/bazelrc/correctness.bazelrc
 
-# Support for debugging NodeJS tests
-# Add the Bazel option `--config=debug` to enable this
-# --test_output=streamed
-#     Stream stdout/stderr output from each test in real-time.
-#     See https://docs.bazel.build/versions/master/user-manual.html#flag--test_output for more details.
-# --test_strategy=exclusive
-#     Run one test at a time.
-# --test_timeout=9999
-#     Prevent long running tests from timing out
-#     See https://docs.bazel.build/versions/master/user-manual.html#flag--test_timeout for more details.
-# --nocache_test_results
-#     Always run tests
-# --node_options=--inspect-brk
-#     Pass the --inspect-brk option to all tests which enables the node inspector agent.
-#     See https://nodejs.org/de/docs/guides/debugging-getting-started/#command-line-options for more details.
-# --define=VERBOSE_LOGS=1
-#     Rules will output verbose logs if the VERBOSE_LOGS environment variable is set. `VERBOSE_LOGS` will be passed to
-#     `nodejs_binary` and `nodejs_test` via the default value of the `default_env_vars` attribute of those rules.
-# --compilation_mode=dbg
-#     Rules may change their build outputs if the compilation mode is set to dbg. For example,
-#     mininfiers such as terser may make their output more human readable when this is set. `COMPILATION_MODE` will be passed to
-#     `nodejs_binary` and `nodejs_test` via the default value of the `default_env_vars` attribute of those rules.
-#     See https://docs.bazel.build/versions/master/user-manual.html#flag--compilation_mode for more details.
-test:debug --test_output=streamed --test_strategy=exclusive --test_timeout=9999 --define=VERBOSE_LOGS=1
-# Use bazel run with `--config=debug` to turn on the NodeJS inspector agent.
-# The node process will break before user code starts and wait for the debugger to connect.
-run:debug --define=VERBOSE_LOGS=1 -- --node_options=--inspect-brk
-# The following option will change the build output of certain rules such as terser and may not be desirable in all cases
-build:debug --compilation_mode=dbg
+# Import Aspect recommended Bazel performance settings for all projects
+import %workspace%/.aspect/bazelrc/performance.bazelrc
 
-# Turn off legacy external runfiles
-# This prevents accidentally depending on this feature, which Bazel will remove.
-build --nolegacy_external_runfiles
+# Import Aspect recommended Bazel debug settings for all projects
+import %workspace%/.aspect/bazelrc/debug.bazelrc
 
-# Turn on --incompatible_strict_action_env which was on by default
-# in Bazel 0.21.0 but turned off again in 0.22.0. Follow
-# https://github.com/bazelbuild/bazel/issues/7026 for more details.
-# This flag is needed to so that the bazel cache is not invalidated
-# when running bazel via `npm bazel`.
-# See https://github.com/angular/angular/issues/27514.
-build --incompatible_strict_action_env
-run --incompatible_strict_action_env
+# Import Aspect recommended Bazel javascript settings for all projects
+import %workspace%/.aspect/bazelrc/javascript.bazelrc
 
 build --action_env GH_TOKEN
 build --action_env PATH
-run --action_env WOOSMAP_PUBLIC_API_KEY
-run --action_env WOOSMAP_PRIVATE_API_KEY
+build --enable_runfiles
+run --define WOOSMAP_PUBLIC_API_KEY=
+run --define WOOSMAP_PRIVATE_API_KEY=
+test --define WOOSMAP_PUBLIC_API_KEY=
+test --define WOOSMAP_PRIVATE_API_KEY=
 
-# Load any settings specific to the current user
-# .bazelrc.user should appear in .gitignore so that settings are not shared with team members
-# This needs to be last statement in this
-# config, as the user configuration should be able to overwrite flags from this file.
-# See https://docs.bazel.build/versions/master/best-practices.html#bazelrc
-# (Note that we use .bazelrc.user so the file appears next to .bazelrc in directory listing,
-# rather than user.bazelrc as suggested in the Bazel docs)
 try-import %workspace%/.bazelrc.user
+
+common --@aspect_rules_ts//ts:skipLibCheck=always

.github/workflows/release.yml

@@ -17,13 +17,13 @@ jobs:
       - uses: actions/checkout@v4
         with:
           token: ${{ secrets.WOOSMAP_GH_ACCESS_TOKEN }}
-      - run: npm ci
-      - run: npm run build -- --jobs 8
-        env:
-          GH_TOKEN: ${{ secrets.WOOSMAP_GH_ACCESS_TOKEN }}
-      - run: npm test -- --jobs 8
-        env:
-          GH_TOKEN: ${{ secrets.WOOSMAP_GH_ACCESS_TOKEN }}
+      - uses: pnpm/action-setup@v4
+        with:
+          version: 9.15.9
+      - name: Install dependencies
+        run: pnpm i --frozen-lockfile
+      - run: pnpm run build
+      - run: pnpm test
       - name: Semantic Release
         uses: cycjimmy/semantic-release-action@v4
         with:

.github/workflows/test.yml

@@ -6,16 +6,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - run: npm ci
-      - run: npm run build -- --profile /tmp/bazel-profile-build.gz --jobs 8
-        env:
-          GH_TOKEN: ${{ secrets.WOOSMAP_GH_ACCESS_TOKEN }}
-      - run: npm test -- --jobs 8
-        env:
-          GH_TOKEN: ${{ secrets.WOOSMAP_GH_ACCESS_TOKEN }}
-      - name: Upload Bazel profiles
-        uses: actions/upload-artifact@v4
+      - uses: pnpm/action-setup@v4
         with:
-          name: bazel profiles
-          path: |
-            /tmp/bazel-profile-*.gz
+          version: 9.15.9
+      - name: Install dependencies
+        run: pnpm i --frozen-lockfile
+      - run: pnpm run build
+      - run: pnpm test

.github/workflows/update-dist.yml

@@ -11,17 +11,19 @@ jobs:
           token: ${{ secrets.WOOSMAP_GH_ACCESS_TOKEN }}
           repository: ${{ github.event.client_payload.pull_request.head.repo.full_name }}
           ref: ${{ github.event.client_payload.pull_request.head.ref }}
-      - run: npm ci
+      - uses: pnpm/action-setup@v4
+        with:
+          version: 9.15.9
+      - name: Install dependencies
+        run: pnpm i --frozen-lockfile
       - name: Update dist
         run: |
-          npm run build
+          pnpm run build
           git config --global user.name 'gaelsimon'
           git config --global user.email 'gael.simon@woosmap.com'
           git add dist
           git commit -m "chore: update dist folder [skip ci]" || true
           git push origin
-        env:
-          GH_TOKEN: ${{ secrets.WOOSMAP_GH_ACCESS_TOKEN }}
       - name: Add reaction
         uses: peter-evans/create-or-update-comment@v2
         with:

.npmrc

@@ -0,0 +1 @@
+hoist=false