Skip to content

Fix angular integration test staging timeout#1250

Open
tnikolova82 wants to merge 1 commit into
masterfrom
fix-angular-fixture-timeout
Open

Fix angular integration test staging timeout#1250
tnikolova82 wants to merge 1 commit into
masterfrom
fix-angular-fixture-timeout

Conversation

@tnikolova82
Copy link
Copy Markdown
Contributor

Summary

  • Strip the angular_dotnet fixture to the minimum needed to pass the integration test, fixing staging timeouts (>15 min)
  • Remove bloated dependencies (bootstrap, jquery, oidc-client, karma, etc.) reducing npm packages from ~939 to ~876
  • Remove unused components (counter, fetch-data, home, nav-menu) and build cache files that were accidentally committed
  • Add @types/node version override and skipLibCheck for TypeScript 4.6 compatibility

Problem

The "deploying an angular app" integration test (node_test.go) was timing out during staging because npm install + ng build --prod of the bloated Angular 13 fixture exceeded the 15-minute CF staging timeout. The fixture included unnecessary dependencies and components that aren't needed for the test assertion (<title>source_app</title>).

Verification

Build tested locally — ng build --configuration production completes in ~18 seconds with the simplified fixture.

The angular integration test was timing out (>15 min) during staging
because the fixture had a bloated dependency tree (~939 npm packages
including bootstrap, jquery, oidc-client, karma, etc.).

Strip the fixture to the minimum needed: core Angular packages only,
single component, no routing/http/forms. This reduces npm install +
ng build time significantly while preserving the test assertion
(<title>source_app</title>).

- Remove unused deps: bootstrap, jquery, oidc-client, popper, karma, etc.
- Remove unused components: counter, fetch-data, home, nav-menu
- Remove SpaProxy NuGet package
- Add @types/node override for TypeScript 4.6 compatibility
- Add skipLibCheck to tsconfig
- Simplify Program.cs to static file server only
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant