chore: generate ts declaration files#11
Conversation
but it passed with
I guess it is ok, I would not touch and let tsc handle this => I would have prefered we stick with the previous |
|
Alright, will fix! 👍 |
|
🎉 This PR is included in version 1.7.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
ok it's merged, but @filahf I guess you are right about your concern for the whole string: declare const _default = 'data:application/json;base64,eyJnbH....'it should double the size of the package, even if types will be stripped at the end, so not so bad let's see... |
|
Great, I like the idea of putting the script outside of the makefile. Yea it shouldn't be a problem bundle-wise but I'll try to do some perf testing in a real project with |
|
yea I agree. there is an open issue for this here microsoft/TypeScript#38638 |


EDIT: Now follows #9 but with the
--skipLibCheckflagWe discussedtypeVersionsin #8 andtsc --emitDeclarationin #9.The tsc method introduces another dependency (which would break in CI). It also outputs the entire base64-encoded string as the type, for example:I’m unsure if this could cause performance issues with the tsserver, but it seems somewhat redundant.This PR ensures that each file gets a corresponding declaration file with the following content:Result: