Update import #40
Annotations
10 errors
AVA:
test/easter.ts#L2
Module '"../lib/index.js"' has no exported member 'getEasterDayName'.
|
AVA:
test/easter.ts#L2
Module '"../lib/index.js"' has no exported member 'getEasterSunday'.
|
AVA:
test/easter.ts#L2
Module '"../lib/index.js"' has no exported member 'isHolyWeek'.
|
AVA:
test/day-meta.ts#L2
Module '"../lib/index.js"' has no exported member 'getDayMeta'.
|
AVA:
lib/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './easter.js'?
|
AVA:
lib/index.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './holidays.js'?
|
AVA:
lib/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './fathers-day.js'?
|
AVA:
lib/index.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './mothers-day.js'?
|
AVA:
lib/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './names.js'?
|
AVA:
lib/index.ts#L6
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './significant.js'?
|
Loading