An in-range update of ts-node is breaking the build π¨
Closed this issue Β· 2 comments
The devDependency ts-node was updated from 8.0.2
to 8.0.3
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
ts-node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Release Notes for Relative TypeScript
Added
- Fall back on resolving relative TypeScript packages (normal resolution is from working directory, these two things can be the same in the case of locally installed packages)
Commits
The new version differs by 10 commits.
8706c31
8.0.3
d065dd2
Update README note about relative installations
655c43b
Fallback on resolving TypeScript relatively (#793)
c2ecc7d
Add note about local TypeScript to README (#789)
7414752
Update README with triple-slash directive example (#776)
efaf67a
Add VS Code env note to README (#738)
2609663
Avoid incrementing memory cache unnecessarily
b4bdb08
Specify sensitive file names for document registry
c215693
Utilize TypeScript
sys
better for service host062254f
Conditionally enable
.[tj]sx
extensions
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
After pinning to 8.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependency
ts-node was updated from8.0.3
to8.1.0
.
Your tests are passing again with this update. Explicitly upgrade to this version π