Hello,

We rely on this babel plugin to help with bundling only application code that we use. Does it support the somewhat recent date-fns 2.x release?

Thanks!
David

It looks like it does not work for getISODay

For example is it possible to do this:

import { format as dateFnsFormat } from "date-fns";

dateFnsFormat(new Date(), "yyyy-MM-dd");

In some cases I have same name functions that conflict with "date-fns", so I think it perhaps would be better to support this feature.

Imports of locale aren't working. This:
import en from "date-fns/locale/en"
causes an error:
Error: Cannot find module 'date-fns/locale'.

Should I do the import otherwise, or is it a bug in the plugin? Thanks a lot!

Transform:

import dt from 'date-fns';

const x = dt.addHours(new Date(), 1); 
const y = dt.format(y, 'MM/DD/YYYY');

to

import addHours from 'date-fns/add_hours';
import format from 'date-fns/format';

const x = addHours(new Date(), 1); 
const y = format(y, 'MM/DD/YYYY')

How to configure this plug-in for nextjs 13 ？

Plugin is pretty slow now, (in my case build time increased from 25 to 45 seconds).

Is it possible to speed up plugin at all?

Hi there - it seems like this is doing a module lookup right now to determine the import filename. What about doing it programmatically, seeing as date-fns's filenames follow a pattern:

function importNameToFilename(importName) {
  return 'date-fns/' + importName.replace(/([A-Z])/, '_$1').toLowerCase();
}

importNameToFilename('startOfYear') // "date-fns/start_of_year"
importNameToFilename('differenceInCalendarDays') // "date-fns/difference_in_calendar_days"

It seems like this would address #2.