Skip to content

Commit

Permalink
Update import
Browse files Browse the repository at this point in the history
  • Loading branch information
@OzzyCzech
OzzyCzech committed Apr 11, 2024
1 parent 6d02170 commit 8f7e416
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions lib/index.ts
View file
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
export * from "./easter.js";
export * from "./holidays.js";
export * from "./fathers-day.js";
export * from "./mothers-day.js";
export * from "./names.js";
export * from "./significant.js";
export * from "./shops.js";
export * from "./get-meta.js";
export * from "./easter";

Check failure on line 1 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './easter.js'?

Check failure on line 1 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './easter.js'?

Check failure on line 1 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './easter.js'?

Check failure on line 1 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './easter.js'?

Check failure on line 1 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './easter.js'?

Check failure on line 1 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './easter.js'?

Check failure on line 1 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './easter.js'?

Check failure on line 1 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './easter.js'?

Check failure on line 1 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './easter.js'?
export * from "./holidays";

Check failure on line 2 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './holidays.js'?

Check failure on line 2 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './holidays.js'?

Check failure on line 2 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './holidays.js'?

Check failure on line 2 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './holidays.js'?

Check failure on line 2 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './holidays.js'?

Check failure on line 2 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './holidays.js'?

Check failure on line 2 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './holidays.js'?

Check failure on line 2 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './holidays.js'?

Check failure on line 2 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './holidays.js'?
export * from "./fathers-day";

Check failure on line 3 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './fathers-day.js'?

Check failure on line 3 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './fathers-day.js'?

Check failure on line 3 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './fathers-day.js'?

Check failure on line 3 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './fathers-day.js'?

Check failure on line 3 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './fathers-day.js'?

Check failure on line 3 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './fathers-day.js'?

Check failure on line 3 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './fathers-day.js'?

Check failure on line 3 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './fathers-day.js'?

Check failure on line 3 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './fathers-day.js'?
export * from "./mothers-day";

Check failure on line 4 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './mothers-day.js'?

Check failure on line 4 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './mothers-day.js'?

Check failure on line 4 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './mothers-day.js'?

Check failure on line 4 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './mothers-day.js'?

Check failure on line 4 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './mothers-day.js'?

Check failure on line 4 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './mothers-day.js'?

Check failure on line 4 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './mothers-day.js'?

Check failure on line 4 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './mothers-day.js'?

Check failure on line 4 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './mothers-day.js'?
export * from "./names";

Check failure on line 5 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './names.js'?

Check failure on line 5 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './names.js'?

Check failure on line 5 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './names.js'?

Check failure on line 5 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './names.js'?

Check failure on line 5 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './names.js'?

Check failure on line 5 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './names.js'?

Check failure on line 5 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './names.js'?

Check failure on line 5 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './names.js'?

Check failure on line 5 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './names.js'?
export * from "./significant";

Check failure on line 6 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './significant.js'?

Check failure on line 6 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './significant.js'?

Check failure on line 6 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './significant.js'?

Check failure on line 6 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on ubuntu-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './significant.js'?

Check failure on line 6 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './significant.js'?

Check failure on line 6 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 20 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './significant.js'?

Check failure on line 6 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './significant.js'?

Check failure on line 6 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './significant.js'?

Check failure on line 6 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on macos-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './significant.js'?
export * from "./shops";

Check failure on line 7 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './shops.js'?

Check failure on line 7 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './shops.js'?
export * from "./get-meta";

Check failure on line 8 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 18 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './get-meta.js'?

Check failure on line 8 in lib/index.ts

View workflow job for this annotation

GitHub Actions / Node.js 21 on windows-latest 

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './get-meta.js'?

0 comments on commit 8f7e416

Please sign in to comment.