-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
TypeScript 5.1: ts.createLiteral is not a function #53077
Labels
Working as Intended
The behavior described is the intended behavior; this is not a bug
Comments
This function has been marked deprecated since 4.1 (possibly earlier?)
|
RyanCavanaugh
added
the
Working as Intended
The behavior described is the intended behavior; this is not a bug
label
Mar 3, 2023
Wowser! Thanks |
johnnyreilly
added a commit
to TypeStrong/ts-loader
that referenced
this issue
Mar 3, 2023
johnnyreilly
added a commit
to TypeStrong/ts-loader
that referenced
this issue
Mar 4, 2023
#1574) * fix: createLiteral removed in 5.1 microsoft/TypeScript#53077 (comment) * fix: factory
This was referenced Mar 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
🔎 Search Terms
ts.createLiteral is not a function
🕗 Version & Regression Information
I noticed that the
typescript@next
test packs for ts-loader were failing with the esoteric errorts.createLiteral is not a function
. I'm baffled as to why - so I thought I'd ask!https://github.com/TypeStrong/ts-loader/actions/runs/4321988253/jobs/7543877954
💻 Code
https://github.com/TypeStrong/ts-loader/blob/9aa5b521a7647fdbd575bb76daa94183e3286604/test/execution-tests/loaderOptions/uppercaseStringLiteralTransformer.js#L10
The tests make use of this API - ts-loader itself does not.
🙁 Actual behavior
Tests that usually pass now fail
🙂 Expected behavior
Tests that usually pass still pass
The text was updated successfully, but these errors were encountered: