You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to use Typia in a project that is stuck at TypeScript 4.7.4 due to other dependencies. I found the compatible versions of ts-patch (2.1.0) and typia (5.0.2) but the setup script installs the latest TS and ts-patch and doesn't allow me to run the patch step on its own.
I expect there are many projects with production constraints keeping them at older versions of TypeScript, it would be nice to be able to use Typia in these projects. Of course it is fine for the latest version of a library to target the latest version of the compiler, but projects that are willing to live with an older version of Typia should be able to use it with the version of TypeScript from back then.
The text was updated successfully, but these errors were encountered:
Thank you for the response (and for the library)! The manual setup doesn't work either because typia patch says it is called with the wrong command. I ended up having to use generation mode instead.
What would help is to for the documentation to be clear that transform mode is really for TS5 and generation mode is for TS<5 and other compilers.
Question
I would like to use Typia in a project that is stuck at TypeScript 4.7.4 due to other dependencies. I found the compatible versions of ts-patch (2.1.0) and typia (5.0.2) but the setup script installs the latest TS and ts-patch and doesn't allow me to run the patch step on its own.
I expect there are many projects with production constraints keeping them at older versions of TypeScript, it would be nice to be able to use Typia in these projects. Of course it is fine for the latest version of a library to target the latest version of the compiler, but projects that are willing to live with an older version of Typia should be able to use it with the version of TypeScript from back then.
The text was updated successfully, but these errors were encountered: