Shouldn't the timezone be considered? about ical-generator HOT 4 CLOSED

As long as using UTC datetimes works in nearly every client I would stick to this solution, because it's not possible to detect the end users location and timezone right now.

Did you have any issues with UTC dates?

from ical-generator.

Yeah, at the moment timezone support is fudged a bit (I wrote this bit). Using UTC is obviously not correct, but neither is using the local time set on the Date object, because the timezone being output in the ical file will not necessarily be the machine's local date, and JS Date objects can only be either UTC or local time. It seemed to be more straightforward and predictable to use UTC dates in this case.

I think the solution would be to pull in moment-timezone as a dependency for proper timezone handling. I started sketching this out at on #38 but maybe I should finish it off.

from ical-generator.

+1 to using moment-timezone. It's what I'm using in srct/schedules and it's a bit hard to follow what happens to the timezones and the times themselves between going into and out ical-generator.

from ical-generator.

ical-generator 3.0 now uses moment-timezone, so this issue should be fixed. You can test the current develop with npm i ical-generator@next.

from ical-generator.