Great, thanks for the update.
The system.js module loader used in the original tutorial (https://code.daypilot.org/67423/angular-2-scheduler-tutorial-typescript) requires something similar - you have to add a reference to daypilot-angular.min.js manually to systemjs.config.js otherwise the daypilot js file doesn't get loaded.
Webpack used in projects created by Angular CLI seems to be somewhat smarter and loads the library automatically - it looks like it uses information from daypilot-pro-angular/package.json where it is specified:
{
"name": "daypilot-pro-angular",
"version": "8.2.2386",
"description": "DayPilot Pro for JavaScript (Angular 2)",
"main": "daypilot-angular.min.js",
"typings": "daypilot-angular.min.d.ts",
"module": "daypilot-angular.min.js",
"private": true,
"files": [
"daypilot-angular.min.d.ts",
"daypilot-angular.min.js"
],
"peerDependencies": {
"@angular/core": "^2.0.0",
"@angular/platform-browser": "^2.0.0"
},
"peerDependencies": {
"@angular/core": "^2.0.0",
"@angular/platform-browser": "^2.0.0"
},
"author": "Annpoint, s.r.o.",
"license": "SEE LICENSE IN LicenseAgreement.pdf"
}
I have to admit that some Angular 2 aspects still involve a great deal of black magic for me so there might be some hidden quirks. So if there is any problem just let me know!