Skip to content

Update dependency ts-node to ~8.10.0#174

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/ts-node-8.x
Open

Update dependency ts-node to ~8.10.0#174
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/ts-node-8.x

Conversation

@renovate
Copy link

@renovate renovate bot commented Jul 10, 2023

This PR contains the following updates:

Package Change Age Confidence
ts-node (source) ~8.8.2~8.10.0 age confidence

Release Notes

TypeStrong/ts-node (ts-node)

v8.10.2

Compare Source

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)

v8.10.1: Fix breaking change for require('ts-node/*')

Compare Source

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)

v8.10.0: Experimental native ESM support

Compare Source

Added

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

v8.9.1: Fix --interactive / -i flag so it forces REPL even when stdin is not a TTY

Compare Source

Fixed

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

v8.9.0

Compare Source

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)


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Author

renovate bot commented Jul 10, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @agm/core@3.0.0-beta.0
npm ERR! Found: @angular/common@15.2.10
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"^15.2.10" from the root project
npm ERR!   peer @angular/common@"^15.0.0 || ^16.0.0" from @angular/cdk@15.2.9
npm ERR!   node_modules/@angular/cdk
npm ERR!     @angular/cdk@"^15.2.9" from the root project
npm ERR!     peer @angular/cdk@"15.2.9" from @angular/material@15.2.9
npm ERR!     node_modules/@angular/material
npm ERR!       @angular/material@"^15.2.9" from the root project
npm ERR!       1 more (ngx-ui-tour-md-menu)
npm ERR!     1 more (ngx-ui-tour-md-menu)
npm ERR!   17 more (@angular/forms, @angular/material, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/core@3.0.0-beta.0
npm ERR! node_modules/@agm/core
npm ERR!   @agm/core@"^3.0.0-beta.0" from the root project
npm ERR!   peer @agm/core@"3.0.0-beta.0" from @agm/snazzy-info-window@3.0.0-beta.0
npm ERR!   node_modules/@agm/snazzy-info-window
npm ERR!     @agm/snazzy-info-window@"^3.0.0-beta.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/common@10.2.5
npm ERR! node_modules/@angular/common
npm ERR!   peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/core@3.0.0-beta.0
npm ERR!   node_modules/@agm/core
npm ERR!     @agm/core@"^3.0.0-beta.0" from the root project
npm ERR!     peer @agm/core@"3.0.0-beta.0" from @agm/snazzy-info-window@3.0.0-beta.0
npm ERR!     node_modules/@agm/snazzy-info-window
npm ERR!       @agm/snazzy-info-window@"^3.0.0-beta.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-12-11T17_05_37_772Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-12-11T17_05_37_772Z-debug-0.log

@renovate renovate bot force-pushed the renovate/ts-node-8.x branch 2 times, most recently from 2954c20 to 41a486d Compare July 11, 2023 07:36
@renovate renovate bot force-pushed the renovate/ts-node-8.x branch 2 times, most recently from 6bd8df2 to c4a19f1 Compare July 28, 2023 06:13
@renovate renovate bot force-pushed the renovate/ts-node-8.x branch from c4a19f1 to 77d81ca Compare November 5, 2023 10:43
@renovate renovate bot changed the title chore(deps): update dependency ts-node to ~8.10.0 Update dependency ts-node to ~8.10.0 Nov 5, 2023
@renovate renovate bot changed the title Update dependency ts-node to ~8.10.0 chore(deps): update dependency ts-node to ~8.10.0 Nov 7, 2023
@renovate renovate bot force-pushed the renovate/ts-node-8.x branch 2 times, most recently from 4b83938 to df0a8bd Compare November 20, 2023 18:47
@renovate renovate bot force-pushed the renovate/ts-node-8.x branch from df0a8bd to 8e25fbe Compare December 11, 2023 17:05
@renovate renovate bot changed the title chore(deps): update dependency ts-node to ~8.10.0 Update dependency ts-node to ~8.10.0 Dec 31, 2024
@renovate renovate bot force-pushed the renovate/ts-node-8.x branch from 8e25fbe to 189389d Compare August 10, 2025 14:38
@renovate
Copy link
Author

renovate bot commented Aug 10, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @agm/core@3.0.0-beta.0
npm error Found: @angular/common@15.2.10
npm error node_modules/@angular/common
npm error   @angular/common@"^15.2.10" from the root project
npm error   peer @angular/common@"^15.0.0 || ^16.0.0" from @angular/cdk@15.2.9
npm error   node_modules/@angular/cdk
npm error     @angular/cdk@"^15.2.9" from the root project
npm error     peer @angular/cdk@"15.2.9" from @angular/material@15.2.9
npm error     node_modules/@angular/material
npm error       @angular/material@"^15.2.9" from the root project
npm error       1 more (ngx-ui-tour-md-menu)
npm error     1 more (ngx-ui-tour-md-menu)
npm error   17 more (@angular/forms, @angular/material, ...)
npm error
npm error Could not resolve dependency:
npm error peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/core@3.0.0-beta.0
npm error node_modules/@agm/core
npm error   @agm/core@"^3.0.0-beta.0" from the root project
npm error   peer @agm/core@"3.0.0-beta.0" from @agm/snazzy-info-window@3.0.0-beta.0
npm error   node_modules/@agm/snazzy-info-window
npm error     @agm/snazzy-info-window@"^3.0.0-beta.0" from the root project
npm error
npm error Conflicting peer dependency: @angular/common@10.2.5
npm error node_modules/@angular/common
npm error   peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/core@3.0.0-beta.0
npm error   node_modules/@agm/core
npm error     @agm/core@"^3.0.0-beta.0" from the root project
npm error     peer @agm/core@"3.0.0-beta.0" from @agm/snazzy-info-window@3.0.0-beta.0
npm error     node_modules/@agm/snazzy-info-window
npm error       @agm/snazzy-info-window@"^3.0.0-beta.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-02-02T21_02_32_328Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-02T21_02_32_328Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants