Refactor: Convert CommonJS to ECMAScript Modules (ESM) #3578
node.js.yml
on: pull_request
lint
45s
format
40s
prod_test_npm
39s
prod_test_binary
40s
test
41s
Annotations
30 errors and 15 warnings
prod_test_npm:
src/components/config/compact-config.ts#L26
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../interfaces/probe.js'?
|
prod_test_npm:
src/components/config/compact-config.ts#L28
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../utils/pino.js'?
|
prod_test_npm:
src/components/config/compact-config.ts#L138
Parameter 'r' implicitly has an 'any' type.
|
prod_test_npm:
src/components/config/compact-config.ts#L139
Parameter 'r' implicitly has an 'any' type.
|
prod_test_npm:
src/components/config/compact-config.ts#L142
Parameter 'r' implicitly has an 'any' type.
|
prod_test_npm:
src/components/config/compact-config.ts#L143
Parameter 'r' implicitly has an 'any' type.
|
prod_test_npm:
src/components/config/compact-config.ts#L149
Parameter 'r' implicitly has an 'any' type.
|
prod_test_npm:
src/components/config/compact-config.ts#L184
Parameter 'r' implicitly has an 'any' type.
|
prod_test_npm:
src/components/config/compact-config.ts#L185
Parameter 'r' implicitly has an 'any' type.
|
prod_test_npm:
src/components/config/compact-config.ts#L188
Parameter 'r' implicitly has an 'any' type.
|
prod_test_binary:
src/components/config/compact-config.ts#L26
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../interfaces/probe.js'?
|
prod_test_binary:
src/components/config/compact-config.ts#L28
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../utils/pino.js'?
|
prod_test_binary:
src/components/config/compact-config.ts#L138
Parameter 'r' implicitly has an 'any' type.
|
prod_test_binary:
src/components/config/compact-config.ts#L139
Parameter 'r' implicitly has an 'any' type.
|
prod_test_binary:
src/components/config/compact-config.ts#L142
Parameter 'r' implicitly has an 'any' type.
|
prod_test_binary:
src/components/config/compact-config.ts#L143
Parameter 'r' implicitly has an 'any' type.
|
prod_test_binary:
src/components/config/compact-config.ts#L149
Parameter 'r' implicitly has an 'any' type.
|
prod_test_binary:
src/components/config/compact-config.ts#L184
Parameter 'r' implicitly has an 'any' type.
|
prod_test_binary:
src/components/config/compact-config.ts#L185
Parameter 'r' implicitly has an 'any' type.
|
prod_test_binary:
src/components/config/compact-config.ts#L188
Parameter 'r' implicitly has an 'any' type.
|
test:
src/components/config/compact-config.ts#L26
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../interfaces/probe.js'?
|
test:
src/components/config/compact-config.ts#L28
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../utils/pino.js'?
|
test:
src/components/config/compact-config.ts#L138
Parameter 'r' implicitly has an 'any' type.
|
test:
src/components/config/compact-config.ts#L139
Parameter 'r' implicitly has an 'any' type.
|
test:
src/components/config/compact-config.ts#L142
Parameter 'r' implicitly has an 'any' type.
|
test:
src/components/config/compact-config.ts#L143
Parameter 'r' implicitly has an 'any' type.
|
test:
src/components/config/compact-config.ts#L149
Parameter 'r' implicitly has an 'any' type.
|
test:
src/components/config/compact-config.ts#L184
Parameter 'r' implicitly has an 'any' type.
|
test:
src/components/config/compact-config.ts#L185
Parameter 'r' implicitly has an 'any' type.
|
test:
src/components/config/compact-config.ts#L188
Parameter 'r' implicitly has an 'any' type.
|
prod_test_npm
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
prod_test_binary
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
test
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
format
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
lint:
packages/notification/channel/mailgun.ts#L59
Use 'Object.hasOwn()' instead of 'Object.prototype.hasOwnProperty.call()'
|
lint:
src/components/logger/history.ts#L37
Caution: `SQLite3` also has a named export `verbose`. Check if you meant to write `import {verbose} from 'sqlite3'` instead
|
lint:
src/components/notification/schedule-notification.ts#L8
Caution: `cron` also has a named export `schedule`. Check if you meant to write `import {schedule} from 'node-cron'` instead
|
lint:
src/components/probe/index.test.ts#L42
Caution: `pg` also has a named export `Pool`. Check if you meant to write `import {Pool} from 'pg'` instead
|
lint:
src/components/probe/index.test.ts#L57
Unexpected any. Specify a different type
|
lint:
src/components/probe/prober/http/index.test.ts#L54
Unexpected any. Specify a different type
|
lint:
src/components/probe/prober/postgres/index.ts#L7
Caution: `pgConnectionString` also has a named export `parse`. Check if you meant to write `import {parse} from 'pg-connection-string'` instead
|
lint:
src/components/probe/prober/postgres/request.ts#L32
Caution: `pg` also has a named export `Pool`. Check if you meant to write `import {Pool} from 'pg'` instead
|
lint:
src/loaders/jobs.ts#L34
Caution: `cron` also has a named export `schedule`. Check if you meant to write `import {schedule} from 'node-cron'` instead
|
lint:
src/loaders/jobs.ts#L38
Caution: `cron` also has a named export `schedule`. Check if you meant to write `import {schedule} from 'node-cron'` instead
|