Although the original comment said nobody uses those, Google sent me one today (TZID="(UTC-05:00) America/New_York", whatever that might mean).  Changed the split to a regexp.

…always unique).

Conflicts:
	package.json

Close #21.

eg. if we have the following in an ical
```
FREEBUSY;FBTYPE=FREE:
```
We ultimately end up with no start and end date values and it blows up
trying to replace the strings on undefined

Added better support for Recurrence Rules:
- Updates to specific recurrences of events now get their own entries in
a recurrences[] array, keyed by ISO date/time.  (Previously, their
records silently overwrote the main recurrence event)
- Exceptions to recurrences now appear in an exdate[] array, keyed by
ISO date/time.

Also added "knowledge" of the dtstamp, created, and lastmodified fields
so that they get stored as dates, not strings.

This should solve issues #57 and #63.

Code maintenance problems:
* Example.js should be pointing to node-ical, not ical now.
* ical should depend on rrule 2.1.0 or greater due to dependency issues
with underscore

Added tests:
* Verify that a recurrence-id doesn't overwrite the main entry
* Verify that exdates appear in the exdate array
* Verify that recurrence-id entries appear in the recurrences array
* Verify that the arrays are keyed by ISO date strings

Some ical files have a specific RECURRENCE-ID override entry that
appears before the more general RRULE parent entry for the same UID.
There were two bugs related to this:
1) If multiple entries for the same UID appear, the later UID entries
were supposed to overwrite fields from the previous UID entries.  This
wasn't working correctly, so fields weren't getting overwritten.  In
this case, it meant that the RECURRENCE-ID parent entry wasn't getting
the RRULE added to it.
2) The correct behaviour (as far as I can tell) should be for the parent
record to look the same, regardless of which entry comes first, and the
RECURRENCE-ID entry should end up in the recurrences array.  This is now
handled by letting the RECURRENCE-ID entry be the parent *and* an entry
in the array, but then letting the RRULE example overwrite the fields in
the parent as appropriate.

Added a test to demonstrate the case and the correct processing of it.

Some ISPs will return a valid web page for DNS entries that don't exist.
By using an invalid IP address, we can ensure the test fails correctly
in those situations.

Fixed the dates in the newly-added test

…han date objects.

- update travis-ci testing up to nodejs 8
- update dependencies for testing
- add (backwardcompatible) option to process the ICS file asynchronous to prevent blocking the eventloop on very big files

Add asynchronous processing of ICS data, Update travis-ci, dependencies

Last changes introduced bad performance, this is corrected now. So especially big files are handled 5 times faster

0.6.1 with performance optimizations

…SOString is not existing

fix bug and update deps (incl. change uuid lib)

It have to be an object, because it is an associative array.

It's not necessarily a breaking change, but it was just bugging me a little bit :)

…version.

Add missing semicolon in example 1 in README.md

correct datatype

just another datatype correction

ignore time if type is date; add date type info

Add Time Zone Support

…eLines

Refactor and Improve API

Add typescript types

ignored the removal of request as it is definitly required but needs to
be replaced by something else of course.
Merge remote-tracking branch 'upstream/master'