Add Angular SSR monitor-mode integration example - #52
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a runnable Angular SSR app using the published WebDecoy 0.18.0 packages. Middleware observes API and rendered-page requests in monitor mode, logs limited structured decisions, and leaves enforcement disabled. Readers can verify tripwire and rate-limit decisions locally without an API key, with an optional server-only dashboard configuration step.
The example is nested to install independently of workspace packages. It includes a lockfile, startup instructions, SSR hostname configuration, deployment caveats, and no detector changes.
Validation: production build passed; five integration tests passed against the built Node server (SSR HTML, catalog, tripwire, reserved test trigger, rate limit); Chrome hydration/catalog interaction passed with no captured warnings/errors. Cloud reporting was not exercised; tests explicitly clear the API key.