angular 4.0+ calendar

Demo

https://mattlewis92.github.io/angular-calendar/

Table of contents

• About
• Getting started
• Documentation
• FAQ
• Angular 1 version
• Development
• License

About

A calendar component for Angular 4.0+ that can display events on a month, week or day view. The successor of angular-bootstrap-calendar.

Getting started

First install through npm:

npm install --save angular-calendar

Next include the CSS file somewhere into your app:

node_modules/angular-calendar/dist/css/angular-calendar.css

Finally import the calendar module into your apps module:

import { NgModule } from '@angular/core';
import { BrowserAnimationsModule } from '@angular/platform-browser/animations';
import { CalendarModule } from 'angular-calendar';

@NgModule({
  imports: [
    BrowserAnimationsModule,
    CalendarModule.forRoot()
  ]
})
export class MyModule {}

Then you can use the mwl-calendar-month-view, mwl-calendar-week-view and mwl-calendar-day-view components in your app. For a full e2e example see the kitchen sink demo.

Module bundlers

You can find quick start examples for all common module bundlers in the build-tool-examples folder.

Usage without a module bundler

<script src="node_modules/angular-calendar/dist/umd/angular-calendar.js"></script>
<script>
    // everything is exported angularCalendar namespace
</script>

Usage with Angular Universal

See this comment for how to use with Universal.

Documentation

To see all available API options, take a look at the auto generated documentation. You may find it helpful to view the examples on the demo page.

FAQ

Is this library AoT compatible?

Yes.

Does this library work with angular 2.x?

The last version of this library that supports 2.x is 0.9.1. However the upgrade from angular 2.x to 4.x is just a matter of changing the dependencies in your package.json and adding the angular/animations module

How do I use this with my favourite module bundler?

See the examples list.

No styles are appearing?

No component styles are included with each component to make it easier to override them (otherwise you’d have to use !important on every rule that you customised). Thus you need to import the CSS file separately from node_modules/angular-calendar/dist/css/angular-calendar.css.

How come there are so many dependencies?

When building the calendar some parts were found to be reusable so they were split out into their own modules. Only the bare minimum that is required is included with the calendar, there is no extra code than if there were no dependencies. date-fns especially only imports directly the functions it needs and not the entire library.

The month, week or day view doesn’t meet my project requirements, but the other views do.

Build your own component to replace that view, and use it in place of the one this library provides. It’s impossible to provide a calendar component that meets everyones use cases, hopefully though at least some of the day / week / month view components provided can be customised with the calendars API enough to be of some use to most projects.

How come there’s no year view like the ng1 version?

As there are so many events to show on each month, it doesn’t provide a lot of value and is just an extra burden to maintain. There is nothing to stop someone from building a new lib like angular-calendar-year-view though ;)

Does this calendar work with mobile?

This library is not optimised for mobile. Due to the complex nature of a calendar component, it is non trivial to build a calendar that has a great UX on both desktop and mobile. It is recommended to build your own calendar component for mobile that has a dedicated UX. You may be able to get some degree of mobile support by setting some custom CSS rules for smaller screens and including hammerjs but your mileage may vary.

Angular 1 version

https://github.com/mattlewis92/angular-bootstrap-calendar

Development

Prepare your environment

• Install Node.js and NPM (should come with)
• Install local dev dependencies: npm install while current directory is this repo

Development server

Run npm start to start a development server on port 8000 with auto reload + tests.

Testing

Run npm test to run tests once or npm run test:watch to continually run tests.

Release

• Bump the version in package.json (once the module hits 1.0 this will become automatic)

npm run release

License

MIT