-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency ts-node to v10 #204
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/ts-node-10.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #204 +/- ##
=======================================
Coverage 48.03% 48.03%
=======================================
Files 4 4
Lines 127 127
Branches 27 27
=======================================
Hits 61 61
Misses 66 66 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
July 9, 2021 22:37
8d23342
to
1166e35
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
August 9, 2021 00:18
1166e35
to
eeb61f9
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
August 18, 2021 18:05
eeb61f9
to
07a7ed7
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
October 1, 2021 10:34
07a7ed7
to
e303589
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
October 11, 2021 18:11
e303589
to
8c4807b
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
2 times, most recently
from
October 22, 2021 20:54
a33023b
to
9fd89d1
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
January 1, 2022 10:24
9fd89d1
to
7e434cd
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
February 7, 2022 17:01
7e434cd
to
270201a
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
2 times, most recently
from
March 6, 2022 04:46
dd01144
to
930c307
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
May 21, 2022 21:24
930c307
to
1e78038
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
2 times, most recently
from
June 8, 2022 14:06
f6b1d3a
to
6071f3a
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
2 times, most recently
from
July 7, 2022 02:18
c55c7b8
to
791ee6c
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
2 times, most recently
from
July 14, 2022 05:38
741881f
to
5895d70
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
September 2, 2022 09:34
5895d70
to
dacd2d9
Compare
renovate
bot
changed the title
chore(deps): update dependency ts-node to v10
Update dependency ts-node to v10
Dec 17, 2022
renovate
bot
changed the title
Update dependency ts-node to v10
chore(deps): update dependency ts-node to v10
Dec 17, 2022
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
December 8, 2023 13:50
dacd2d9
to
ed7f3df
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^8.10.2
->^10.9.2
Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.
Release Notes
TypeStrong/ts-node (ts-node)
v10.9.2
: Fixtsconfig.json
file not foundCompare Source
Fixed
tsconfig.json
file not found on latest TypeScript version (https://github.com/TypeStrong/ts-node/pull/2091)v10.9.1
Compare Source
Fixed
--esm
--esm
are unaffectedhttps://github.com/TypeStrong/ts-node/milestone/18?closed=1
v10.9.0
Compare Source
Added
--project
accepts path to a directory containing atsconfig.json
(#1829, #1830) @cspotcodeexperimentalTsImportSpecifiers
option which allows using voluntary.ts
file extensions in import specifiers (undocumented except for API docs) (#1815) @cspotcodeFixed
child_process.fork()
would erroneously execute the parent's entrypoint script, not the intended child script (#1812, #1814) @devversion"react-jsx"
and"react-jsxdev"
in swc transpiler (#1800, #1802) @cspotcoderepl.evalCode()
with code not ending in a newline would not update the typechecker accordingly (#1764, #1824) @cspotcodehttps://github.com/TypeStrong/ts-node/milestone/16?closed=1
v10.8.2
Compare Source
Fixed
nyc
code coverage reports had incorrect pathshttps://github.com/TypeStrong/ts-node/milestone/15?closed=1
v10.8.1
Compare Source
Fixed
https://github.com/TypeStrong/ts-node/milestone/14
v10.8.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1767
Added
module=NodeNext
,module=Node16
,.mts
,.cts
,.mjs
, and.cjs
file extensions (#1414, #1694, #1744, #1745, #1727, #1717, #1753, #1757) @cspotcodeexperimentalResolver
(docs)experimentalResolver
, will be enabled by default in a future version (docs)import "./foo.js"
will executefoo.ts
See also: TypeScript issue #37582import "./foo.ts"
experimentalSpecifierResolution
(#1727, #1753) @cspotcode--experimental-specifier-resolution
(Node docs)tsconfig.json
for convenience, to avoid the CLI flagdiagnostics
property toTSError
, with array of TypeScript diagnostic objects from the compiler (API docs) (#1705, #1706) @paulbrimicombeChanged
experimentalResolverFeatures
toexperimentalResolver
(docs) (#1727) @cspotcodeshortCircuit: true
(#1714, #1715) @cspotcodeFixed
.type
command was not showing any type information when using TypeScript nightly builds (#1761, #1762) @cspotcodepreferTsExts
combined with third-party transpiler hooks could disruptnyc
code coverage (#1755) @cspotcodefile://
URLs in stack traces did not always use percent-encoding (#1738, #1726, #1729) @cspotcodeDocs
--project
is-P
, not-p
(#1731, #1734) @lobsterkatiehttps://github.com/TypeStrong/ts-node/milestone/12
v10.7.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1680
Added
--esm
flag, option, andts-node-esm
binary (#1258, #1655)esm
support; no need for--loader
norNODE_OPTIONS
#!/usr/bin/env ts-node-esm
, runts-node --esm
, or add to your tsconfig.json:"ts-node": {"esm": true}
Changed
--experimental-json-modules
Fixed
https://github.com/TypeStrong/ts-node/milestone/11
v10.6.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1666
Added
mocha
with--loader ts-node/esm
, where previously node would throw[ERR_UNKNOWN_FILE_EXTENSION]
--loader
with an extensionless entrypoint causes this error nodejs/node#33226mocha
, have an extensionless entrypoint. (source, source)NODE_OPTIONS=--loader ts-node/esm
with these tools causes this error. mochajs/mocha#4645moduleTypes
overrides (#1650)Fixed
--swc
and other third-party transpilers did not respectmoduleTypes
overrides (#1651, #1652, #1660)process.execArgv
(#1657, #1658)child_process.fork()
, since it usesprocess.execArgv
to create a similar child runtime.child_process.fork()
will preserve both node flags andts-node
hooks.https://github.com/TypeStrong/ts-node/milestone/9
v10.5.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1634
Added
transpileOnly
-style transformation.isolatedModules
. This will only affect rare cases such as usingconst enums
withpreserveConstEnums
disabled.swc: true
convenience option (docs) (#1487, #1536, #1613, #1627)"swc": true
or--swc
will use swc for faster execution@swc/core
or@swc/wasm
dependencies from your project before falling-back to global installations (#1613, #1627)traceResolution
output (docs) (#1128, #1491) @TheUnlockedts-node -vvv
also logs absolute paths tots-node
andtypescript
, to make it more obvious when you're accidentally using globally-installed versions (#1323, #1620)Changed
v8-compile-cache-lib
to load typescript--camelCase
and--hyphen-case
for all CLI flags; update documentation to use--camelCase
(#1598, #1599)TSError
diagnosticText
property non-enumerable to prevent it from being logged below the stack (#1632)Fixed
undefined
for all inputs after the first when using swc transpiler (#1478, #1580, #1602)--showConfig
output, emit accuratemoduleTypes
paths resolved relative to thetsconfig.json
which declared them (#1389, #1619)ts-node --help
output (#1597, #1600)tsconfig.schemastore-schema.json
(#1425, #1618)"use strict"
emit in SWC transpiler (#1531, #1537)ERR_UNKNOWN_FILE_EXTENSION
constructor; was throwingERR_UNKNOWN_FILE_EXTENSION is not a constructor
(#1562) @blueloversDocs
env -S
flag for shebangs (docs) (#1448, #1545) @sheeit, @cheeskipIgnore
when you want to compile files in node_modules (docs) (#1553) @webstrandmoduleTypes
on options page (docs) (#1630, #1633)Misc
experimentalResolverFeatures
option, but it does not do anything yet (#1514, #1614)https://github.com/TypeStrong/ts-node/milestone/4
v10.4.0
Compare Source
Added
Changed
creatEsmHooks
(API docs) (#1506, #1529)Fixed
https://github.com/TypeStrong/ts-node/milestone/8
v10.3.1
Compare Source
Fixed
https://github.com/TypeStrong/ts-node/milestone/7
v10.3.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1507
Added
util.promisify(setTimeout)(1000)
orfs.readFileSync('example.txt')
createEsmHooks()
function to create ESM loader hooks (API docs) (#1439) @nonararegister()
accepts a ts-nodeService
(API docs) (#1474)register(options)
is still supported; no breaking changes--emit
to--help
output (#1400, #1484) @markbradley27Changed
require('source-map-support')
, they will be redirected to@cspotcode/source-map-support
Fixed
source-map-support
instead of@cspotcode/source-map-support
(#1440, #1441, #1438, #1495, cspotcode/node-source-map-support#23, #1496, #1497) @ejose19require('source-map-support')
, they will be redirected to@cspotcode/source-map-support
@cspotcode/source-map-support
for the fixes and enhancements listed here:@cspotcode/source-map-support
changelog100
on first line and* 2
on second line would erronously be interpreted as100 * 2
allowJs
(#1488, #1489)TS_NODE_IGNORE
andTS_NODE_IGNORE_DIAGNOSTICS
; treat empty environment variable as empty array (#1301, #1483) @ValeriaVGTS_NODE_IGNORE= ts-node ./example.ts
will disable default ignore rules; will compile files in./node_modules
Docs
https://github.com/TypeStrong/ts-node/milestone/5
v10.2.1
Compare Source
Fixed
https://github.com/TypeStrong/ts-node/milestone/6
v10.2.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1423
Added
--no-experimental-repl-await
,experimentalReplAwait
, orTS_NODE_EXPERIMENTAL_REPL_AWAIT
(CLI docs, API docs)"pretty": false
disables pretty formatting of diagnostics even when stdout is a TTY (#1418, #1420) @elevatebartpretty
option, not to be confused with TypeScript'spretty
optionconst foo = 1
in the REPL,foo
is unused. We ignore the resulting diagnosticfoo is declared but its value is never read
Fixed
--loader
async
annotations (#1405, #1410)require.resolve
error when@types/node
peerDependency is missing (#1419, #1422)https://github.com/TypeStrong/ts-node/milestone/2
v10.1.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1390
Added
"moduleType"
option to override module type -- CommonJS or ECMAScript -- on select files. (docs) (#1342, #1371, #1376)webpack.config.ts
, must execute as CommonJS but the rest of the project is ESMpackage.json
"type"
andtsconfig.json
"module"
.cjs
and.mjs
extensions, but for.ts
and.tsx
files"extends"
support for"ts-node"
options intsconfig.json
(#1328, #1356)"ts-node": {}
options will be parsed from extended tsconfigsscope
andscopeDir
; add both to CLI andtsconfig.json
options; un-deprecateTS_NODE_SCOPE
env var; addTS_NODE_SCOPE_DIR
env var (docs) (#1346, #1367)Changed
"ts-node"
object at the top of--showConfig
output instead of the bottom (#1355)Fixed
[stdin]
,[eval]
, and<repl>
contexts (#1333)ts-node -e
__filename
,__dirname
,module
and sub-fields ofmodule
,exports
, and builtin module aliasesfs
, etckeepClassNames
totrue
(#1344)Docs
node --loader ts-node/esm
(docs) (#1379)https://github.com/TypeStrong/ts-node/milestone/3
v10.0.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1337
Breaking changes are prefixed with [BREAKING]
Added
--show-config
to log the resolved configuration (docs) (#1100, #1243)swc
integration and new--transpiler
option to use third-party transpilers for a massive speed boost on large codebases (docs) (#779, #1160)scopeDir
API option (docs) (#1155)projectSearchDir
API option (docs) (#1155)--cwd-mode
andts-node-cwd
to resolve config file relative to cwd, not entrypoint script (#1155)Changed
--script-mode
default behavior; resolve tsconfig relative to entrypoint script instead of cwd (#949, #1197, #1155)$PATH
, becausets-node
will respect the script's localtsconfig.json
--cwd-mode
orts-node-cwd
if you need legacy behaviorignore
rules evaluate relative totsconfig.json
directory, otherwisecwd
(#1155)--dir
to--cwd
; renameTS_NODE_DIR
toTS_NODE_CWD
(#1155)--dir
andTS_NODE_DIR
are deprecated but still parsed for backwards-compatibility--dir
effectively changed the working directory ofts-node
; renaming makes this behavior more obviousDeprecated
TS_NODE_SCOPE
(#1155)--dir
andTS_NODE_DIR
(#1155)Removed
DEFAULTS
,normalizeSlashes
,parse
,split
ts-node
's programmatic APIFixed
ERR_REQUIRE_ESM
when attempting to execute ESM as CJS, even when not using--loader ts-node/esm
(#1232)node
compiler
is loaded relative totsconfig.json
instead of entrypoint script (#1155)ts-node ./index
may execute the wrong file extension because tsconfig search poisons therequire.resolve
cache (#1155)Docs
CONTRIBUTING.md
to document the codebase and our development workflowhttps://github.com/TypeStrong/ts-node/milestone/1
v9.1.1
Compare Source
No code changes. We re-packed and republished v9.1.1, because the v9.1.0 package was broken due to an npm v7 bug.
Fixes
v9.1.0
Compare Source
Added
--typeCheck
flag to override--transpileOnly
flag specified intsconfig.json
(#1142)Changed
Register
toService
. It is still aliased asRegister
for backwards compatibility (#1158)Fixed
--es-module-specifier-resolution
as an alias of--experimental-specifier-resolution
for node 12 compatibility (#1122) @nguyensomniacDocs
ts-node-dev
in README (#1131) @iamandrewlucatransformers
description to clarify incompatibility withtranspileOnly
(#1123)Misc
v9.0.0
Compare Source
Breaking changes are labelled [BREAKING] below.
Added
ERR_REQUIRE_ESM
when a file isrequire()
d which should be loaded as ESM (#1031)"exports"
declaration to package.json in backwards-compatible way, enablingnode --loader ts-node/esm
without file extension (#1028)"require"
option via tsconfig (#925)NODE_NO_READLINE
environment variable (#1090)node --loader ts-node/esm/transpile-only
(#1102) @concisionChanged
Fixed
realpath
, which should fix workflows that use symlinks, such aspnpm
, Lerna workspaces, or other mono-repo configurations (#970)node_modules
when--skip-ignore
or--ignore
options are configured to allow it (#970)getSourceFileNames
/rootNames
(#999)projectVersion
every timegetSourceFileNames
changes, avoiding accidentally outdated typechecking (#998)ts.transpileModule
(#1054) @thetutlage--experimental-specifier-resolution
coming fromNODE_OPTIONS
in ESM loader (#1085) @evg656e.cjs
,.mjs
, and any unexpected file extensions (#1103) @concisionDocs
Configuration
📅 Schedule: Branch creation - "on the 1st through 7th day of the month" in timezone America/Los_Angeles, 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.
This PR was generated by Mend Renovate. View the repository job log.