function getMonthName(monthNumber) {
  const date = new Date();
  date.setMonth(monthNumber - 1);

  return date.toLocaleString([], { month: 'long' });
}

The current day of month will have an impact on the behavior of this method. Conceptually it will add the number of days given by the current day of the month to the 1st day of the new month specified as the parameter, to return the new date. For example, if the current value is 31st January 2016, calling setMonth with a value of 1 will return 2nd March 2016. This is because in 2016 February had 29 days.

  • ☆ Yσɠƚԋσʂ ☆@lemmy.mlOP
    27·
    1 year ago

    One month after any given day of the month is, by most people’s intuition, a valid thing to ask for.

    Nobody actually thinks this way, when you ask somebody what’s the next month they don’t go, oh today is the x day of the month and I’m going to add days to the current date to see what’s the next month. That’s not how vast majority of people think about this intuitively. Clearly you and people who designed Js Date API do though.

    “a month is 31 days in January, and 28 or 29 in February, so adding a month does different things in different months”

    That’s how months work. Each month has a different number of days.

    If I say to add four days, will it throw an exception if it’s the 31st? No month has 35 days, so I should get an exception, right?

    Yeah, it’s how months work.

    In fact, this isn’t a hypothetical argument this is how date APIs work in sane languages like Java. For example:

    java.time.LocalDate.of(2023, 2, 31)
> java.time.DateTimeException: Invalid date 'FEBRUARY 31'

java.time.LocalDate.of(2023, 2, 3)
> #object[java.time.LocalDate 0x2bc77260 "2023-02-03"]

    The fact that you think what Js API dies is preferable to this is frankly surreal to me.