No default export (1.8.4)

With v1.8.4 I got the following error:

import dayjs from 'dayjs';

Module ‘“…/node_modules/dayjs/index”’ has no default export.

[roblevintennis]

Yes, I’m getting this. I don’t have time to setup a toy repo and everything, but will post some screenshots of what I’m seeing:

Using:

import * as dayjs_ from 'dayjs';
console.log('daysjs before: ', dayjs)
debugger;
const dayjs = (dayjs_).default || dayjs_;
console.log('daysjs after: ', dayjs)
debugger;

I see it’s undefined until I apply the .default workaround others have mentioned:

The logs in ^ should show that just doing import * as dayjs_ from 'dayjs'; in webpack results in undefined—looks like it’s considering it a default export.

But even when I attempt to use es6 import default approach (e.g. import dayjsAsDefault from 'dayjs';), it doesn’t get fully resolved. This is after such import:

and dayjsAsDefault is undefined

Personally, I’d reopen this until it’s proven to work with Webpack given the popularity of that bundler but up to maintainer of course 😉 For now, we’ll all have imports with comments pointing to this issue

[neemzy]

IMO this shouldn’t be closed. Pre-1.8.4 behaviour (import dayjs from "dayjs";) is still broken and this is a BC break. We are using dayjs in several in-house apps and packages which depend on each other, and this has just broken our entire stack with a single dependency update. We would really appreciate not having to spend a whole day editing our import code / editing package.json to use a fixed 1.8.3 version on every single app/package.

Would you please consider going the extra mile to try and make import and require behaviours both work as intended? I can try to help if you give me a few pointers about the specific problem. Thanks a ton!