Bug Report: Build and Publish Failures After Adding Playwright Tests (node_modules\rxfire\firestore\lite\interfaces.d.ts)
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- angular, playwright, typescript
- Domain
- build-system, ci-cd, testing
Research direction
Start by reproducing the pipeline after adding the Playwright tests, focusing on the failing build and publish steps. Inspect the reported node_modules\rxfire\firestore\lite\interfaces.d.ts location and the pipeline configuration; done means both steps complete successfully without the reported errors.
Written by the indexing model from the issue text.
Description
Bug Report: Build and Publish Failures After Adding Playwright Tests
Environment:
- Angular: ^16.0.0
- Firebase: 9.8.0
- AngularFire: 7.6.1
- Windows: 11
- Node.js: 20.11.1
- playwright: 1.45.2",
- playwright/test: ^1.45.2,
- elopment",
"test": "npx playwright test"
},
Description:
After adding Playwright tests to the pipeline, the tests pass successfully. However, during the build and publish steps, errors occur, causing the steps to fail.
Steps to Reproduce:
- Add Playwright tests to the pipeline.
- Run the pipeline.
- Observe the build and publish steps.
Expected Behavior:
The build and publish steps should complete successfully without any errors after adding Playwright tests.
Actual Behavior:
The following errors occur during the build and publish steps:
Location of this file
\node_modules\rxfire\firestore\lite\interfaces.d.ts
Screenshots:
Additional Context:
Please review and address this issue.
- Dominant language
- TypeScript
- Stars
- 7.8k
- Forks
- 2.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 25
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from angular/angularfire
-
comp: compat comp: firestore comp: storage type: chore
Difficulty 4/5 3-5 days Newbie friendliness 48/100
angular/angularfire#3822 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
angular/angularfire#3800 · 1 reaction ·
Maintainers usually reply within 3 days
-
Use `TransferState` to hand server-rendered Firestore data to the browser, instead of reading every document twiceMay be free again @armando-navarro claimed this 75 days ago, and no pull request is open. Opencomp: firestore comp: ssr priority: P0 (critical) type: feature version: current (v17+)
angular/angularfire#3757 · 1 assignee ·
Maintainers usually reply within 3 days
-
Six `firebase` entry points have no `@angular/fire` equivalent, so their exports are unreachableMay be free again @armando-navarro claimed this 75 days ago, and no pull request is open. Opencomp: core type: feature
angular/angularfire#3755 · 1 assignee ·
Maintainers usually reply within 3 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
angular/angularfire#3737 · 4 comments · 26 reactions ·
Maintainers usually reply within 3 days
All issues in angular/angularfire
Similar issues
-
bug parity
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
WenyuChiou/agent-board#1489 ·
Maintainers usually reply within 1 day
-
area: bazaar bug complexity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
accensa/x402-facilitator-stellar#779 ·
Maintainers usually reply within 1 day
-
bug good first issue P4 size:S web-ui
Difficulty 2/5 Half a day Newbie friendliness 85/100
josephfung/curia#2600 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cloudflare/partykit#444 ·