update readme #26
Annotations
10 errors
build:
src/handlers/nasa/eonet.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../index.js'?
|
build:
src/handlers/nasa/eonet.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../setup.js'?
|
build:
src/handlers/nasa/eonet.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../utils/api-client.js'?
|
build:
src/handlers/nasa/donki.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../index.js'?
|
build:
src/handlers/nasa/donki.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../setup.js'?
|
build:
src/handlers/nasa/donki.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../utils/api-client.js'?
|
build:
src/handlers/nasa/cmr.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../index.js'?
|
build:
src/handlers/nasa/apod.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../utils/api-client.js'?
|
build:
src/handlers/jpl/scout.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../setup.js'?
|
build:
src/handlers/jpl/scout.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../utils/api-client.js'?
|