add: Initial create order implementation (WIP) #24
Annotations
90 errors
build (ubuntu-latest, 22):
src/client/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (ubuntu-latest, 22):
src/client/order.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (ubuntu-latest, 22):
src/client/order.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.
|
build (ubuntu-latest, 22):
src/core/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (ubuntu-latest, 22):
src/core/order.ts#L2
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (ubuntu-latest, 22):
src/core/order.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (ubuntu-latest, 22):
src/core/order.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/nostr.js'?
|
build (ubuntu-latest, 22):
src/utils/crypto.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (ubuntu-latest, 22):
src/utils/nostr.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (ubuntu-latest, 22):
test/core/order.test.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 18):
src/client/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (macos-latest, 18):
src/client/order.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (macos-latest, 18):
src/client/order.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.
|
build (macos-latest, 18):
src/core/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (macos-latest, 18):
src/core/order.ts#L2
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 18):
src/core/order.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (macos-latest, 18):
src/core/order.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/nostr.js'?
|
build (macos-latest, 18):
src/utils/crypto.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 18):
src/utils/nostr.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 18):
test/core/order.test.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 20):
src/client/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (macos-latest, 20):
src/client/order.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (macos-latest, 20):
src/client/order.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.
|
build (macos-latest, 20):
src/core/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (macos-latest, 20):
src/core/order.ts#L2
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 20):
src/core/order.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (macos-latest, 20):
src/core/order.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/nostr.js'?
|
build (macos-latest, 20):
src/utils/crypto.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 20):
src/utils/nostr.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 20):
test/core/order.test.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 22):
src/client/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (macos-latest, 22):
src/client/order.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (macos-latest, 22):
src/client/order.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.
|
build (macos-latest, 22):
src/core/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (macos-latest, 22):
src/core/order.ts#L2
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 22):
src/core/order.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (macos-latest, 22):
src/core/order.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/nostr.js'?
|
build (macos-latest, 22):
src/utils/crypto.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 22):
src/utils/nostr.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (macos-latest, 22):
test/core/order.test.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (ubuntu-latest, 20):
src/client/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (ubuntu-latest, 20):
src/client/order.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (ubuntu-latest, 20):
src/client/order.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.
|
build (ubuntu-latest, 20):
src/core/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (ubuntu-latest, 20):
src/core/order.ts#L2
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (ubuntu-latest, 20):
src/core/order.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (ubuntu-latest, 20):
src/core/order.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/nostr.js'?
|
build (ubuntu-latest, 20):
src/utils/crypto.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (ubuntu-latest, 20):
src/utils/nostr.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (ubuntu-latest, 20):
test/core/order.test.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (ubuntu-latest, 18):
src/client/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (ubuntu-latest, 18):
src/client/order.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (ubuntu-latest, 18):
src/client/order.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.
|
build (ubuntu-latest, 18):
src/core/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (ubuntu-latest, 18):
src/core/order.ts#L2
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (ubuntu-latest, 18):
src/core/order.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (ubuntu-latest, 18):
src/core/order.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/nostr.js'?
|
build (ubuntu-latest, 18):
src/utils/crypto.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (ubuntu-latest, 18):
src/utils/nostr.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (ubuntu-latest, 18):
test/core/order.test.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 18):
src/client/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (windows-latest, 18):
src/client/order.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (windows-latest, 18):
src/client/order.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.
|
build (windows-latest, 18):
src/core/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (windows-latest, 18):
src/core/order.ts#L2
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 18):
src/core/order.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (windows-latest, 18):
src/core/order.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/nostr.js'?
|
build (windows-latest, 18):
src/utils/crypto.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 18):
src/utils/nostr.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 18):
test/core/order.test.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 22):
src/client/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (windows-latest, 22):
src/client/order.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (windows-latest, 22):
src/client/order.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.
|
build (windows-latest, 22):
src/core/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (windows-latest, 22):
src/core/order.ts#L2
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 22):
src/core/order.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (windows-latest, 22):
src/core/order.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/nostr.js'?
|
build (windows-latest, 22):
src/utils/crypto.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 22):
src/utils/nostr.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 22):
test/core/order.test.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 20):
src/client/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (windows-latest, 20):
src/client/order.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
build (windows-latest, 20):
src/client/order.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.
|
build (windows-latest, 20):
src/core/order.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (windows-latest, 20):
src/core/order.ts#L2
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 20):
src/core/order.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/core/order.js'?
|
build (windows-latest, 20):
src/core/order.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/nostr.js'?
|
build (windows-latest, 20):
src/utils/crypto.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 20):
src/utils/nostr.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|
build (windows-latest, 20):
test/core/order.test.ts#L1
Cannot find module 'nostr-tools' or its corresponding type declarations.
|