Comments (5)
Hi, we'll need more info on your issue. If you could provide a stackblitz repro or a github repo that reproduces your issue we'll be able to investigate it.
Without this, it is hardly actionnable to us. Thank you.
from angular.
In addition to what @JeanMeche said, moving directly from v11 to v17 is not a migration path that we support or recommend. Migrations should be done one major version at a time.
from angular.
@JeanMeche - I'll work on getting a reproducible example.
@atscott - Yeah, I've been upgrading in steps, however I'm not sure at which stage the issue starting popping up. I didn't get it build-ready until I completed the upgrade process.
from angular.
Closing since we cannot investigate without a reproduction. Please feel free to open a new issue if you are able to provide one.
from angular.
We recently encountered a familiar issue while running unit tests after migrating Angular from version 16 to 17 and updating Zone to version 0.14. Our development team faced significant challenges debugging this issue, but we were able to find a solution. We discovered that removing the zone.js
plugin import 'zone.js/plugins/zone-patch-rxjs'
from polyfills.ts
resolved the issue, and everything returned to normal. I hope that will help someone else.
from angular.
Related Issues (20)
- Add distinction between model() and model.required() on type level HOT 1
- Standalone Component Exports HOT 1
- Set ViewEncapsulation per module HOT 2
- setting signal outside of angular zone error HOT 3
- View provider/provider info that's logged in the console is incorrect
- No more subclasses or `implements`/`extends` information in API doc
- Missing code blocks in usage notes. HOT 1
- toSignal does not change if new published value passes equality check and there is no way to modify that HOT 2
- ErrorNG8001 ${element} is not know element HOT 11
- FormGroup.reset() input typings are incorrect HOT 2
- ErrorHandler docs don't have standalone alternative HOT 2
- Allow one time binding input HOT 1
- Missing example code for accessibility best practices case study HOT 1
- PromiseRejectionEvent not fired
- feat(signal_effect with explicit deps): introduce a new "watch" func having explicit signal_deps and skipFirstCallback HOT 4
- Generate Error routes at build time.
- Page not found for https://angular.dev/assets/tutorials/common HOT 1
- @for and ngFor reporting errors but still iterating over data HOT 5
- optionalChainNotNullable does not seems to work HOT 6
- MathML is unsupported HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from angular.