Repository navigation
[Bug]: platform-browser-dynamic #18
Description
Checklist
- I have searched the existing issues and have not found a duplicate
- I have read the README and documentation and have not found a solution
- I agree to follow the OpenNG Foundation Code of Conduct
What happened?
Is this issue really resolved? When I delete the deprecated package @angular/platform-browser-dynamic from our project tests using spectator fail.
ERROR] Could not resolve "@angular/platform-browser-dynamic/testing"
node_modules/@openng/spectator/fesm2022/openng-spectator.mjs:7:44:
7 │ ...icTestingModule } from '@angular/platform-browser-dynamic/testing';
You can mark the path "@angular/platform-browser-dynamic/testing" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.
Is this expected? Do I have to follow the suggested solution? I would rather expect that spectator works without @angular/platform-browser-dynamic out of the box.
Any help appreciated.
Steps to reproduce
- Remove @angular/platform-browser-dynamic
- Run tests
Expected behavior
I would expect that spectator works without having the deprecated package @angular/platform-browser-dynamic included in package.json.
Actual behavior
Tests fail with:
ERROR] Could not resolve "@angular/platform-browser-dynamic/testing"
node_modules/@openng/spectator/fesm2022/openng-spectator.mjs:7:44:
7 │ ...icTestingModule } from '@angular/platform-browser-dynamic/testing';
You can mark the path "@angular/platform-browser-dynamic/testing" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.
Minimal reproduction
https://github.com/openng-org/spectator/issues
Library version
1.0.1
Angular version
22.1.3
Node version
26.7.0
Package manager
npm
Browser(s)
Chrome
Environment details
Angular application setup
None
Angular context
- SSR (Server-Side Rendering) is involved
- Zoneless change detection is enabled
Relevant log output
Screenshots
No response
Additional context
No response
Activity
Martinspire commentedon Oct 5, 2026
Well, there hasn't been a release yet, so no this hasn't been fixed in the package, but it has been fixed in the code. Not sure why they didn't release yet...
geromegrignon commentedon Oct 6, 2026
Hi @LukasMachetanz, the new 1.0.2 version includes the fix.
Martinspire commentedon Oct 7, 2026
I see 1.0.1 on Github but 1.0.2 on NPM?