Uh oh!
There was an error while loading. Please reload this page.
chore: test using node 16, remove node 10 - #862
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@## main #862 +/- ##
=======================================
Coverage 95.85% 95.85% =======================================
Files 31 31 Lines 940 940 =======================================
Hits 901 901 Misses 39 39 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
targos
commented
May 5, 2021
Change LGTM but we need to understand why it fails on v16 and fix that |
targos
commented
May 5, 2021
targos
commented
May 5, 2021
/cc @MylesBorins could it be a breaking change from npm v7 ? |
MylesBorins
commented
May 7, 2021
@targos I'll take a look to see how this broke. We had been testing npm 7 and CITGM when it first landed on master, but it is possible that something regressed. |
MylesBorins
commented
May 7, 2021
@targos I'm getting an even earlier failure with v16.1.0 😅 |
BethGriggs
commented
May 7, 2021
@MylesBorins that error looks similar to tapjs/tapjs#624 (comment) / tapjs/tapjs#746 |
MylesBorins
commented
May 7, 2021
hmmm maybe we need to update tap in CITGM? |
MylesBorins
commented
May 7, 2021
I have a reproduction for the npm team and we've found where this regressed. Hopefully a fix won't be terribly difficult |
wraithgar
commented
May 7, 2021
This was only working by coincidence pre-7.8.0. Based on how it was "working" before, we may want to think about running commands from a |
targos
commented
Jun 12, 2021
Given the results in #866, npm is fixed so I'm landing this PR. |

10 is EOL, and 16 is new and shiny? 😀
Possibly blocked by #852?
Checklist
npm testpasseshere