Open
Description
Environment
Please provide as many details as you can:
- Hosting type
- Form.io
- Local deployment
- Version:
- Formio.js version:
- Frontend framework:
- Browser:
- Browser version:
Steps to Reproduce
Expected behavior
Observed behavior
Example
If possible, please provide a screenshot, live example (via JSFiddle or similar), and/or example code to help demonstrate the issue.
For code or form JSON, please enclose in a code block:
'Log files:
C:\Users\msuzen\AppData\Local\npm-cache\_logs\2025-02-25T19_40_58_734Z-debug-0.log
# npm resolution error report
While resolving: flobi-web@0.0.0
Found: @angular/core@17.3.12
node_modules/@angular/core
@angular/core@"^17.3.12" from the root project
peer @angular/core@"^16.0.0 || ^17.0.0 || ^18.0.0" from @formio/angular@7.5.0
node_modules/@formio/angular
@formio/angular@"*" from the root project
peer @angular/core@"17.3.12" from @angular/[email protected]
node_modules/@angular/common
@angular/common@"^17.3.12" from the root project
peer @angular/common@"^16.0.0 || ^17.0.0 || ^18.0.0" from @formio/angular@7.5.0
node_modules/@formio/angular
@formio/angular@"*" from the root project
Could not resolve dependency:
peer @angular/core@"18.2.13" from @angular/[email protected]
node_modules/@angular/elements
peer @angular/elements@"^16.0.0 || ^17.0.0 || ^18.0.0" from @formio/angular@7.5.0
node_modules/@formio/angular
@formio/angular@"*" from the root project
Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.