Skip to content
CI

feat: add eslint-config for zotero-plugin #199

Sign in to view logs

feat: add eslint-config for zotero-plugin

feat: add eslint-config for zotero-plugin #199

Triggered via pull request February 3, 2025 13:13
@northwordnorthword
synchronize #91
eslint-config
Status Failure
Total duration 27s
Artifacts –

ci.yml

on: pull_request
build
15s
build
lint
17s
lint
test
18s
test
docs
0s
docs
publish
0s
publish
Fit to window
Zoom out
Zoom in

Annotations

9 errors
build
An import path can only end with a '.ts' extension when 'allowImportingTsExtensions' is enabled.
build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../globs.js'?
build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types.js'?
build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../globs.js'?
build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './configs/ignores.js'?
build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './configs/javascript.js'?
build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './configs/specialCases.js'?
build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './configs/typescript.js'?
build
Process completed with exit code 2.