An in-range update of ts-node is breaking the build π¨
Closed this issue Β· 3 comments
Version 6.1.0 of ts-node was just published.
Branch | Build failing π¨ |
---|---|
Dependency |
ts-node
|
Current Version | 6.0.5 |
Type | devDependency |
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
TypeScript Error FormattingChanged
- Use TypeScript error formatting for diagnostic ouput
- Delete
declarationMap
option from input configuration underts-node
Commits
The new version differs by 5 commits.
ee5c1b3
6.1.0
57f09b5
Remove
declarationMap
from config (#602)70d68ef
Document
-T
alias in README (#600)6c610b4
Use
NODE=stable
tag over specific version (#598)2e44bc0
Use
ts.formatDiagnostics
over of custom function (#597)
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 6.0.5 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 6.1.1 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
Remove `emitDeclarationOnly`Fixed
- Delete
emitDeclarationOnly
from configuration to ensure config is valid
Version 6.1.2 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
CLI FlagsFixed
- Correct CLI default flags using environment variables
- Use
buffer-from
module for old-node.js compatibility
Added
- Awesome new logo to README!