search

coding-blocks / judge-api

7 stars 27 forks source link

An in-range update of ts-node is breaking the build 🚨 #56

Open greenkeeper[bot] opened 4 years ago

greenkeeper[bot] commented 4 years ago

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency ts-node was updated from 8.8.2 to 8.9.0.

🚨 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 - ❌ **ci/circleci: build:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/coding-blocks/judge-api/398?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).
Release Notes for v8.9.0

Fixed

Fix failing tests caused by recent changes to @types/node (#1016)
Fix #945: Bump source-map-support dependency to include upstream fix for worker threads error handling (#1015) @addaleax
Fix #1004: in --scriptMode, resolve config file relative to realpath of entrypoint script (#1009)
Normalized filenames in cache to fix performance issues on Windows (#997) @sylc

Added

Add timestamps to debug logging (#994) @sylc

Docs

Improve coverage of the README (#1000) @KasparEtter
Change order of install commands in README (#993) @jacobdcastro
Mention ts-node -vv flag in issue template (#1001)
Run GHActions tests on pull requests (#1017)

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

After pinning to 8.8.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 4 years ago

Your tests are still failing with this version. Compare changes

Release Notes for Fix `--interactive` / `-i` flag so it forces REPL even when stdin is not a TTY

Fixed

Fix --interactive / -i flag so it forces REPL even when stdin is not a TTY (#1019)

greenkeeper[bot] commented 4 years ago

Your tests are still failing with this version. Compare changes

Release Notes for Experimental native ESM support

Added

Experimental support for native ECMAScript modules in node >=13 (#1007, #1010)

greenkeeper[bot] commented 4 years ago

Your tests are still failing with this version. Compare changes

Release Notes for Fix breaking change for require('ts-node/*')

Fix

Fixes #1026: revert the addition of package.json "exports" because it blocked require()s that used to work, for example require('ts-node/register') (#1027)

greenkeeper[bot] commented 4 years ago

Your tests are still failing with this version. Compare changes

Release Notes for v8.10.2

Fixed

Fixes #1037: source maps broken on Windows. (#1038)

Misc

Fix failing tests on node 6 (#1035)
Push coverage from Github Actions; remove TravisCI (#1034)
Run tests e2e against an npm pack && npm installed ts-node (#1032)
Run CI tests on Windows (#1041)
Run CI only once per commit on pull requests and master (#1042)