Update peer dependencies to enable angular 14
sergiotome opened this issue · 23 comments
Bug Reports
Angular complains about fullcalendar dependencies when upgrading to Angular 14. However, when using the --force attribute everything still works fine. This is something that we can do locally, but cannot do automatically on the CI/CD pipelines though, not allowing us to build the project when angular 14 is used.
Feature Requests
Update peer dependencies in package.json to include angular 14
Any update on this?
Bump on this
I fixed my CI/CD pipelines by downgrading Node.js to 16.15.0. Not sure if this workaround will work for everybody else though.
please do not specify an upper version limit, angular releases every 6 months a major version...so every 6 month the same annoying story! :(
fullcalendar is the only library i use, which does this.
e.g.: https://github.com/DevExpress/devextreme-angular/blob/master/packages/devextreme-angular/package.json
with ivy distribution it should look like this:
"peerDependencies": {
"@angular/common": ">12.0.0",
"@angular/core": ">12.0.0"
},
Thank you
full calendar seems to be working with angular 14 (I have to force the package install ) so i might be a good idea to update the dependencies.
I don't know if thare are any problem with angular 14 (tests not passing ...).
Do we have a date on when this will be solved ?
Angular released 14.1 already. Are there any updates on enabling support for that version any time soon?
UP
UP
there actually is a braking change that forces to patch node modules of fullcalendar removing css imports form main.js (multiple) - it can be done using patch-package to automate but is cumbersome.
Hey,
I'm getting this on ionic-angular
Found: @angular/common@14.1.1
npm ERR! node_modules/@angular/common
npm ERR! @angular/common@"^14.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"9 - 13" from @fullcalendar/angular@5.11.2
npm ERR! node_modules/@fullcalendar/angular
npm ERR! @fullcalendar/angular@"^5.11.2" from the root project
This likely means that the library (@fullcalendar/angular/) which declares FullCalendarModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.
Any help?
Hey, I'm getting this on ionic-angular
Found: @angular/common@14.1.1 npm ERR! node_modules/@angular/common npm ERR! @angular/common@"^14.0.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer @angular/common@"9 - 13" from @fullcalendar/angular@5.11.2 npm ERR! node_modules/@fullcalendar/angular npm ERR! @fullcalendar/angular@"^5.11.2" from the root projectThis likely means that the library (@fullcalendar/angular/) which declares FullCalendarModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.
Any help?
There are two issues here. The one in your screenshot refers to the issue discussed here, for which I haven't seen an update in more than a month. The other one is the issue discussed here: #396 (comment)
Hello @arshaw,
I know that you are probably working on the ivy version, which is nice, but is it possible to release this #408 as a minor version, and when the ivy version is ready, release it as major one, please ?
Also, the company I'm working at, uses the paid version, is it the same thing as the free one in terms of requesting new features/releases ? Because this library is the only one holding us from upgrading to Angular 14 and using all the new features.
Thanks in advance.
@morfems have you tried migrating from @fullcalendar/angular to @fullcalendar/web-component?
See: #403 (comment)
Thanks @nunoarruda for the suggestion 👍. Actually no, I didn't, I wasn't aware of the existence of this package. I think I am going to test it locally and wait for the stable version to use in prod.
Angular v14 instructions are here:
https://fullcalendar.io/docs/v6/angular
Using @beta versions of the web-component and plugins seems to work nicely.
We are using full calendar as a peer dependency of the PrimeNG Ultima theme.
We would like to upgrade to the latest version, but we don't want to use a @beta version.
Any idea when the final version will be released?
It has been almost 4 months since Angular 14 was released and as of now we only have a beta version that works with it. Many people won't want to use a beta version of code in their production releases, and therefore, is there a roadmap about when a final solution will be available to support, not only Angular 14, but any future Angular release going forward (v15 will be out there soon!!)?
BUMP
We are also anxiously awaiting the official production release compatible with v14.x as we actively upgrade from Angular v8 to v14. Thanks
Did anyone make a pull request ?
After testing @fullcalendar/web-component, it works just fine, but there is no way we are going to prod with a beta version.
V6 in the roadmap was scheduled for Q3, we are now in Q4 and we have no information when the stable version will be available. The beta version was up for some time, why not ship it as stable if there are no regressions ?
It makes it hard to purchase more licenses or even recommend fullcalendar to others. And as others mentioned, angular v15 is almost here, and we are still putting on hold migrating to angular 14 because of this library alone.
For now, all we ask for is some responses, you can't keep people hanging, we have our roadmaps too. Thanks
I've updated the peerDependency to support Angular 14. See FullCalendar v5.11.3
Please be aware of the external CSS workaround needed for Angular 14, described in this issue