fable 3.0.80 → 3.0.81

package/dist/fable.compatible.js

@@ -3320,13 +3320,14 @@ var tmpChunkSize=typeof pChunkSize=='number'?pChunkSize:0;var tmpChunkCache=type
 var tmpDateParts=pISOString.split(/\D+/);// Set up a date object with the current time.
 var tmpReturnDate=new Date();// Track the number of hours we need to adjust the date by based on the timezone.
 var tmpTimeZoneOffsetInHours=0;// Track the number of minutes we need to adjust the date by based on the timezone.
-var tmpTimeZoneOffsetInMinutes=0;// Manually parse the parts of the string and set each part for the
+var tmpTimeZoneOffsetInMinutes=0;// This fixes an inconsistency with constructing the date programmatically.
+tmpReturnDate.setUTCDate(1);// Manually parse the parts of the string and set each part for the
 // date. Note: Using the UTC versions of these functions is necessary
 // because we're manually adjusting for time zones stored in the
 // string.
 tmpReturnDate.setUTCFullYear(parseInt(tmpDateParts[0]));// The month numbers are one "off" from what normal humans would expect
 // because January == 0.
-tmpReturnDate.setUTCMonth(parseInt(tmpDateParts[1]-1));tmpReturnDate.setUTCDate(parseInt(tmpDateParts[2]));// Set the time parts of the date object.
+tmpReturnDate.setUTCMonth(parseInt(tmpDateParts[1])-1);tmpReturnDate.setUTCDate(parseInt(tmpDateParts[2]));// Set the time parts of the date object.
 tmpReturnDate.setUTCHours(parseInt(tmpDateParts[3]));tmpReturnDate.setUTCMinutes(parseInt(tmpDateParts[4]));tmpReturnDate.setUTCSeconds(parseInt(tmpDateParts[5]));tmpReturnDate.setUTCMilliseconds(parseInt(tmpDateParts[6]));// If there's a value for either the hours or minutes offset.
 if(tmpDateParts[7]||tmpDateParts[8]){// If there's a value for the minutes offset.
 if(tmpDateParts[8]){// Convert the minutes value into an hours value.