feat!: update build to esm (#58) #38
sckvAnnotations
10 errors
|
Release:
src/middlewares/cookies/cookie-manager.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './signer.js'?
|
|
Release:
src/logger/serializers.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
Release:
src/logger/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../env.js'?
|
|
Release:
src/logger/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './serializers.js'?
|
|
Release:
src/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
Release:
src/index.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
Release:
src/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './request.js'?
|
|
Release:
src/index.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './server.js'?
|
|
Release:
src/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './server.js'?
|
|
Release:
src/context/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './execution.js'?
|