Debian Package Tracker
Register | Log in
Subscribe

ts-node

TypeScript execution and language shell

Choose email to subscribe with

general
  • source: ts-node (main)
  • version: 10.9.2+~cs64.13.43-2
  • maintainer: Debian Javascript Maintainers (archive) (DMD)
  • uploaders: Julien Puydt [DMD]
  • arch: all
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 9.1.1-4
  • oldstable: 10.9.1+~cs8.8.29-1
  • stable: 10.9.2+~cs64.13.20-2
  • testing: 10.9.2+~cs64.13.43-1
  • unstable: 10.9.2+~cs64.13.43-2
versioned links
  • 9.1.1-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 10.9.1+~cs8.8.29-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 10.9.2+~cs64.13.20-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 10.9.2+~cs64.13.43-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 10.9.2+~cs64.13.43-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • ts-node (2 bugs: 0, 1, 1, 0)
action needed
Fails to build during reproducibility testing normal
A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!
Created: 2026-06-28 Last update: 2026-06-29 14:31
debian/patches: 1 patch to forward upstream low

Among the 7 debian patches available in version 10.9.2+~cs64.13.43-1 of the package, we noticed the following issues:

  • 1 patch where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2024-12-16 Last update: 2026-05-05 23:30
testing migrations
  • excuses:
    • Migration status for ts-node (10.9.2+~cs64.13.43-1 to 10.9.2+~cs64.13.43-2): BLOCKED: Rejected/violates migration policy/introduces a regression
    • Issues preventing migration:
    • ∙ ∙ Autopkgtest for moment-timezone.js/0.6.2+dfsg-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-ajv/8.20.0~ds+~cs6.1.3-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-approximate-now/1.0.2-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-braintree-sanitize-url/7.1.1-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-clipanion/3.2.1+dfsg-3: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-compare-versions/5.0.1-3: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-config/3.3.10-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-crc/4.3.2-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-cronstrue/2.21.0-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-dts-bundle-generator/9.5.1-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-entities/4.5.0+dfsg-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-external-editor/3.1.0+dfsg-3: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-file-uri-to-path/2.0.0-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-glob/13.0.6+~cs0.4.15-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-home-assistant-js-websocket/9.6.0-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-import-local/3.2.0+~cs2.0.3-3: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-jest/29.6.2~ds6+~cs73.45.28-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-js-sdsl/4.1.4-4: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-jsdom/20.0.3+~cs124.18.21-6: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-mkdirp/3.0.1+~cs5.2.1-3: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered, s390x: Test triggered (will not be considered a regression) ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for node-mocks-http/1.17.2-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-path-scurry/2.0.2-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-peek-readable/3.1.4-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-postcss/8.5.15+~cs9.3.39-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-recast/0.23.4-5: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-redis/4.6.14+~1.1.2-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-require-dir/1.2.0+~1.0.4-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-resolve-import/2.4.0+~4.0.0-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-rimraf/6.1.3-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-rollup-pluginutils/5.0.2~ds+~2.8.2-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-sinclair-typebox/0.24.44-4: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-smart-buffer/4.2.0-4: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-socks/2.8.8-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-tap/16.3.7+ds3+~cs49.5.20-7: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-tap-parser/13.0.1+~cs4.1.3-5: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-tldts/7.0.30-1: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-token-types/2.1.1+~cs0.2.0-3: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-ts-patch/3.3.0-4: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-tshy/3.3.2+~cs6.0.2-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-typanion/3.14.0+dfsg-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-webfont/11.4.0+dfsg2+~cs35.7.26-19: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for ts-node/10.9.2+~cs64.13.43-2: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, loong64: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
    • ∙ ∙ Lintian check waiting for test results - info
    • ∙ ∙ Too young, only 0 of 5 days old
    • Additional info (not blocking):
    • ∙ ∙ Updating ts-node will fix bugs in testing: #1141030
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/t/ts-node.html
    • ∙ ∙ Reproduced on amd64 - info
    • ∙ ∙ Reproduced on arm64 - info
    • ∙ ∙ Reproduced on armhf - info
    • ∙ ∙ Reproduced on i386 - info
    • Not considered
news
[rss feed]
  • [2026-06-29] Accepted ts-node 10.9.2+~cs64.13.43-2 (source) into unstable (Xavier Guimard)
  • [2026-05-23] ts-node 10.9.2+~cs64.13.43-1 MIGRATED to testing (Debian testing watch)
  • [2026-05-05] Accepted ts-node 10.9.2+~cs64.13.43-1 (source) into unstable (Xavier Guimard)
  • [2026-03-22] ts-node 10.9.2+~cs64.13.20-4 MIGRATED to testing (Debian testing watch)
  • [2026-03-19] Accepted ts-node 10.9.2+~cs64.13.20-4 (source) into unstable (Jérémy Lal)
  • [2025-12-26] ts-node 10.9.2+~cs64.13.20-3 MIGRATED to testing (Debian testing watch)
  • [2025-12-24] Accepted ts-node 10.9.2+~cs64.13.20-3 (source) into unstable (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
  • [2024-12-18] ts-node 10.9.2+~cs64.13.20-2 MIGRATED to testing (Debian testing watch)
  • [2024-12-15] Accepted ts-node 10.9.2+~cs64.13.20-2 (source) into unstable (Ananthu C V)
  • [2024-03-29] ts-node 10.9.2+~cs64.13.20-1 MIGRATED to testing (Debian testing watch)
  • [2024-03-29] ts-node 10.9.2+~cs64.13.20-1 MIGRATED to testing (Debian testing watch)
  • [2024-03-27] Accepted ts-node 10.9.2+~cs64.13.20-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2024-01-24] ts-node 10.9.2+~cs64.13.14-1 MIGRATED to testing (Debian testing watch)
  • [2024-01-22] Accepted ts-node 10.9.2+~cs64.13.14-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-07-20] ts-node 10.9.1+~cs8.8.29-1 MIGRATED to testing (Debian testing watch)
  • [2022-07-17] Accepted ts-node 10.9.1+~cs8.8.29-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-07-13] ts-node 10.8.2+~cs8.8.29-1 MIGRATED to testing (Debian testing watch)
  • [2022-07-13] ts-node 10.8.2+~cs8.8.29-1 MIGRATED to testing (Debian testing watch)
  • [2022-07-04] Accepted ts-node 10.8.2+~cs8.8.29-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-06-15] ts-node 10.8.1+~cs7.8.22-2 MIGRATED to testing (Debian testing watch)
  • [2022-06-09] Accepted ts-node 10.8.1+~cs7.8.22-2 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-06-09] Accepted ts-node 10.8.1+~cs7.8.22-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-06-09] Accepted ts-node 10.8.1+~cs7.0.21-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-06-01] ts-node 10.7.0+~cs7.0.20-3 MIGRATED to testing (Debian testing watch)
  • [2022-05-27] Accepted ts-node 10.7.0+~cs7.0.20-3 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-03-15] ts-node 10.7.0+~cs7.0.20-2 MIGRATED to testing (Debian testing watch)
  • [2022-03-10] Accepted ts-node 10.7.0+~cs7.0.20-2 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-03-09] Accepted ts-node 10.7.0+~cs7.0.20-1 (source) into experimental (Yadd) (signed by: Xavier Guimard)
  • [2022-02-15] ts-node 9.1.1-6 MIGRATED to testing (Debian testing watch)
  • [2022-02-13] Accepted ts-node 9.1.1-6 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • 1
  • 2
bugs [bug history graph]
  • all: 2
  • RC: 0
  • I&N: 1
  • M&W: 1
  • F&P: 0
  • patch: 0
links
  • homepage
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • other distros
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 10.9.2+~cs64.13.20-3build1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing