Skip to content

fix: only error on invalid tsconfig if explicitly passed in (#30) #99

fix: only error on invalid tsconfig if explicitly passed in (#30)

fix: only error on invalid tsconfig if explicitly passed in (#30) #99

Triggered via push May 23, 2024 03:50
Status Success
Total duration 50s
Artifacts

release.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Release: docs/node/esm.md#L87
'loaded' is assigned a value but never used
Release: docs/node/esm.md#L90
'loaded2' is assigned a value but never used
Release: docs/node/ts-import.md#L20
'loaded' is assigned a value but never used
Release: docs/node/ts-import.md#L24
'loadedAgain' is assigned a value but never used
Release: docs/node/ts-import.md#L34
'loaded' is assigned a value but never used
Release: docs/node/tsx-require.md#L19
'tsLoaded' is assigned a value but never used
Release: docs/node/tsx-require.md#L20
'tsFilepath' is assigned a value but never used
Release: docs/node/tsx-require.md#L28
'tsLoaded' is assigned a value but never used
Release: docs/node/tsx-require.md#L29
'tsFilepath' is assigned a value but never used
Release: src/cjs/api/global-require-patch.ts#L7
The 'process.sourceMapsEnabled' is still an experimental feature The configured version range is '>=20.12.2'