0.32.0

[mattlewis92]

Tip

Try out the next version before it's marked as stable with npm i angular-calendar@next

To be in the release (aim is just to get everything modernized and working with the latest angular 20 version rather than any new features):

• remove animations library #1770
• fix: fix scss deprecation warning to prepare for scss v3 #1763
• Upgrade to application builder + migrate away from webpack specific features (how to fix gh-pages deploy)
• Migrate to control flow syntax
• Migrate to inject()
• Migrate to standalone + deprecate CalendarModule
• Fix schematics to work with standalone (allow choosing to add to NgModule or standalone component): ng add fails with standalone application #1699 Boostrap call not found #1719
• Add ng libs as peer dependencies (have schematic add them + upgrade repo to latest): Not working with Angular 19.1.1 / pnpm #1761 v0.29.0: angular-draggable-droppable & angular-resizable-element required to be added to dependencies #1547
• date-fns v2 -> v4 upgrade

[codecov]

Codecov Report

❌ Patch coverage is 97.91667% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 97.91%. Comparing base (dd1ddec) to head (657a720).
⚠️ Report is 33 commits behind head on main.

Files with missing lines	Patch %	Lines
...les/common/calendar-a11y/calendar-a11y.provider.ts	75.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1771      +/-   ##
==========================================
+ Coverage   97.49%   97.91%   +0.41%     
==========================================
  Files          39       42       +3     
  Lines         679      671       -8     
  Branches      143      145       +2     
==========================================
- Hits          662      657       -5     
  Misses          1        1              
+ Partials       16       13       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull Request Overview

This PR updates angular-calendar from version 0.31.1 to 0.32.0, modernizing the codebase to work with Angular 20+ and implementing several architectural improvements including migrating to standalone components, new control flow syntax, and the inject() pattern.

Key changes:

• Migration to standalone components and deprecation of NgModule-based CalendarModule
• Adoption of Angular's new control flow syntax (@if, @for, @switch instead of *ngIf, *ngFor, *ngSwitch)
• Migration from constructor injection to the inject() function pattern
• Update from Sass @import to @use syntax for better module system compliance

Reviewed Changes

Copilot reviewed 269 out of 271 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
tsconfig-date-adapters.json	Updates module and target to ES2015 for modern JavaScript support
projects/demos/styles.scss	Migrates from @import to @use syntax for Sass imports
projects/demos/main.ts	Complete rewrite from NgModule to standalone bootstrapping with provider configuration
projects/demos/index.html	Updates title to reflect Angular 20.2+ compatibility
Multiple template files	Systematic migration to new Angular control flow syntax
Multiple component files	Migration to standalone components with inject() pattern and proper imports
Multiple module files	Removal of NgModule files as part of standalone migration
Multiple sources files	Updates to new import system with text loader attributes

Comments suppressed due to low confidence (1)

projects/demos/main.ts:1

• The @ts-expect-error comment is repeated throughout the codebase. Consider adding a more descriptive comment explaining why TypeScript cannot provide types for the 'with { loader: "text" }' syntax and potentially referencing the relevant TypeScript issue or documentation.

import { enableProdMode, importProvidersFrom } from '@angular/core';

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[atsjo]

everything seems to work fine except my tests, it worked with 31.1, but with next they fail with this error:

SyntaxError: Named export 'getMonthView' not found. The requested module 'calendar-utils' is a CommonJS module, which may not support all module.exports as named exports.

I use nx with vitest via analogjs for testing...

[mattlewis92]

everything seems to work fine except my tests, it worked with 31.1, but with next they fail with this error:

SyntaxError: Named export 'getMonthView' not found. The requested module 'calendar-utils' is a CommonJS module, which may not support all module.exports as named exports.

I use nx with vitest via analogjs for testing...

Any chance you could put together a minimal repro where I can reproduce the issue? I'm not sure what would have changed there to cause this issue (especially as calendar-utils is shipped as dual esm + commonjs so it should be picking up the esm version)

[atsjo]

I'll see if I get time later today or tomorrow...
Seems very easy to reproduce using latest nx with vitest and creating a custom calendar based on angular-calendar@next

[mattlewis92]

I'll see if I get time later today or tomorrow... Seems very easy to reproduce using latest nx with vitest and creating a custom calendar based on angular-calendar@next

I'm unable to reproduce my end - I made a new project via npx create-nx-workspace vitest-angular-test --unitTestRunner=vitest angular-standalone

Installed these deps:

    "angular-calendar": "^0.32.0-next.5",
    "angular-draggable-droppable": "^9.0.1",
    "angular-resizable-element": "^8.0.0",
    "date-fns": "^4.1.0",

Set the root app to:

import { Component } from '@angular/core';
import { RouterModule } from '@angular/router';
import { NxWelcome } from './nx-welcome';
import {
  provideCalendar,
  DateAdapter,
  CalendarMonthViewComponent,
} from 'angular-calendar';
import { adapterFactory } from 'angular-calendar/date-adapters/date-fns';

@Component({
  imports: [NxWelcome, RouterModule, CalendarMonthViewComponent],
  selector: 'app-root',
  template: `
    <mwl-calendar-month-view [viewDate]="viewDate" [events]="events" />
    <app-nx-welcome></app-nx-welcome>
    <router-outlet></router-outlet>
  `,
  styleUrl: './app.scss',
  providers: [
    provideCalendar({
      provide: DateAdapter,
      useFactory: adapterFactory,
    }),
  ],
})
export class App {
  protected title = 'vitest-angular-test';
  viewDate = new Date();
  events = [];
}

and verified vitest was able to run:

[atsjo]

I'm guessing it's only a problem when using pnpm, I'll try and verify

[atsjo]

here is a repro: https://github.com/atsjo/repro.git
clone -> pnpm i -> pnpm nx test repro

Basically the same as you did, but stripped some generated setup, used pnpm and running zoneless...
When running vitest I have to use pool: 'thread' in vitest.config.mts , or else all angulat test fail with

Vitest caught 1 unhandled error during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.
⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯
Error: module is already linked
 ❯ [kLink] ../../node:internal/vm/module:363:19
 ❯ ../../node:internal/vm/module:354:13

if running with pool: 'thread' as in the repro it fails with

SyntaxError: Named export 'getMonthView' not found. The requested module 'calendar-utils' is a CommonJS module, which may not support all module.exports as named exports.

This setup works fine with the former angular-calendar...

[atsjo]

tried using your exact description with npm and minimal changes using zonejs... still the same problem, repro here: https://github.com/atsjo/vitest-angular-test.git

clone -> npm i -> npm exec nx test

I have tested this with node 22.18 and node 24.6, but only on windows...
So the problem is not related to pnpm @mattlewis92

[mattlewis92]

tried using your exact description with npm and minimal changes using zonejs... still the same problem, repro here: atsjo/vitest-angular-test.git

clone -> npm i -> npm exec nx test

I have tested this with node 22.18 and node 24.6, but only on windows... So the problem is not related to pnpm @mattlewis92

Thank you, I was able to reproduce! Hacking around locally I was able to fix the issue by adding an exports to the package.json for calendar-utils (the same as we have for the main package). Honestly I'm a bit confused how this was ever working with the previous version or why it just broke 🤷‍♂️ But it's a simple enough fix, I will get a release out later today

[atsjo]

calendar-utils@0.12.1 fixed the problem with that package, now it fails with the positioning package, requiring the same fix

SyntaxError: Named export 'positionElements' not found. The requested module 'positioning' is a CommonJS module, which may not support all module.exports as named exports.

[mattlewis92]

calendar-utils@0.12.1 fixed the problem with that package, now it fails with the positioning package, requiring the same fix

SyntaxError: Named export 'positionElements' not found. The requested module 'positioning' is a CommonJS module, which may not support all module.exports as named exports.

Thanks, working on it!

[mattlewis92]

@atsjo I just published 0.32.0-next.6 and it now works in your sample project. Thanks for reporting this issue!

[atsjo]

thanks! new version run tests fine in the project I actually use it as well... When will we see a final release @mattlewis92 ?

[mattlewis92]

thanks! new version run tests fine in the project I actually use it as well... When will we see a final release @mattlewis92 ?

Awesome! I just want to test the new version in my work application where we have a heavy usage of this library as well, just to sanity check everything works OK, and then will release as final once I do that sometime in the next few days