Roadmap to stable strip-types #24
Comments
|
I think we should publish the suggested tsconfig on npm and maintain it. Plan sounds good. |
Great idea 🙂 could go under the |
I'm getting back to this tonight. I have made the requested updates locally. Need to finish a couple other things and then will push.
Looks like this is still an unknown: https://bsky.app/profile/jakebailey.dev/post/3lf4igi3lzc2m
I can do! I recently did something similar for one of my own libraries. |
marco-ippolito
changed the title
|
What about TS syntax in the repl? Should that work by default too? |
I did not dare to try implement it in the REPL as it looks quite complicate. |
|
We've named and approved microsoft/TypeScript#59601 which should land in either TS 5.8 or 5.9 depending on timing, so that should be a recommended flag once it's in |
|
On the |
|
Well that was fast: https://devblogs.microsoft.com/typescript/announcing-typescript-5-8-beta/ |
|
Small heads up since it seems to be easy to miss that 5.7 also added I've added a PR in tsconfig/bases#300 to add it already, but thought it was worth mentioning here. |
|
Do you have any insights about the possibility of The existence of this roadmap for type stripping is excellent news, because it means that the feature is likely to become stable and we are already considering it for our projects. I wonder whether there is any similar information about type transformation :) |
|
|
|
Of course note that TS itself is "unstable", so you may end up with a break when using that flag eventually (e.g., we will probably be removing the module keyword to make way for TC39 use). |
We have already removed the |
PR-URL: #57705 Refs: nodejs/typescript#24 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Jordan Harband <ljharb@gmail.com> Reviewed-By: Minwoo Jung <nodecorelab@gmail.com> Reviewed-By: Zijian Liu <lxxyxzj@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
PR-URL: nodejs#57705 Refs: nodejs/typescript#24 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Jordan Harband <ljharb@gmail.com> Reviewed-By: Minwoo Jung <nodecorelab@gmail.com> Reviewed-By: Zijian Liu <lxxyxzj@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
PR-URL: #57705 Refs: nodejs/typescript#24 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Jordan Harband <ljharb@gmail.com> Reviewed-By: Minwoo Jung <nodecorelab@gmail.com> Reviewed-By: Zijian Liu <lxxyxzj@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
PR-URL: #57705 Refs: nodejs/typescript#24 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Jordan Harband <ljharb@gmail.com> Reviewed-By: Minwoo Jung <nodecorelab@gmail.com> Reviewed-By: Zijian Liu <lxxyxzj@gmail.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
|
@marco-ippolito I think we should accelerate the removal of warnings. The dx right not is not great because of them. |
|
I've been testing it for a while in prod and non prod environments and it
seems pretty stable. I haven't had any issues with it running, so I think
it's also super ready for a stable flag
… Message ID: ***@***.***>
|
PR-URL: #58643 Refs: nodejs/typescript#24 Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Jordan Harband <ljharb@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Ethan Arrowood <ethan@arrowood.dev> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
PR-URL: #58643 Refs: nodejs/typescript#24 Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Jordan Harband <ljharb@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Ethan Arrowood <ethan@arrowood.dev> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
Uh oh!
There was an error while loading. Please reload this page.
We have unflagged
--experimental-strip-typesin v23.6.0.Here what I think are some of the next steps:
ERR_INVALID_TYPESCRIPT_SYNTAXfor everything.--erasableSyntaxOnlyflag--erasableSyntaxOnlyflag @khaosdoctor (Add recommended configuration for Node.js running TS natively tsconfig/bases#293)--experimental-strip-types@robpalme added it to https://github.com/tsconfig/bases/blob/main/bases/node-ts.jsonFeel free to add items if you think I missed something
The text was updated successfully, but these errors were encountered: