Not working with TypeScript v5 (author's note)

[nonara]

Update

Beta version is out! See the message below for detail:

• Not working with TypeScript v5 (author's note) #93 (comment)

[moshest]

Thank you for all the effort you put on this.

I just want to raise a point that waiting until the end of April can be too much of a delay for some projects (mine in particular). Given the fact that the beta was released 2 months ago the current situation isn't promising and it may push users to seek for other solutions (including myself).

There is any way we can speed up the migration? 🙏
Can we at least share what's the progress being done and what's still missing?

[nonara]

@moshest

A few points...

1. This is FOSS. In the years this and my other large libraries have been active, I believe $75 in total has been donated from users.

2. I run a company, work 6 days per week, and generally work over 40hrs per week.

3. I will be surrendering significant revenue and time to get this done. As of the last few months, I simply (and literally) could not do this, for reasons which are personal.

Notably, I also had three people who claimed to be willing to help lined up months ago, and all backed out.

I say this with personal respect, but also with the due response to such a message - if you'd like to take your "business" elsewhere, you're more than welcome to do so. However, at present, this is a problem that is not yet solved and is, as I've said, non-trivial.

Lastly, I also think this is important to point out -

If this was an issue that prevented current libraries from working, that is one thing, but rewriting everything to support a new major version is another. The latter is nice to have early, but the worst case scenario is you wait an additional month to use the latest features. It's not ideal, but it may happen from time to time.

Demanding a maintainer work more quickly for free so that you can use the newest features is precisely the sort of thing that I've seen embitter and contribute to the burnout of so many formerly enthusiastic maintainers.

Frankly, I've always tried and have succeeded in keeping up with the changes in the past, but I simply couldn't do it this cycle, because of the extent of changes and personal situations which demanded beyond even normal working hours.

I say this in the hope that you will more carefully consider your tone and demands in the future in this regard.

Lastly, if you'd like a temporary (or permanent) solution, I can suggest writing a script which uses the compiler API, which will allow you to use transformers.

[moshest]

Hi @nonara,

Thank you for the detailed response. As an open-source contributor and library maintainer I know exactly how you feel.

I never meant to ask you to "work faster" and I apologize for the misunderstanding. Please note I asked how can "we" release it faster.

My main feedback is that it's not clear what needed to be done in order to support version 5, nor a clear tasks or milestones that can help a community member such myself to hop on and contribute a few hours on the weekend.

[nonara]

@moshest I appreciate that. Neuledge looks nice, btw!

Unfortunately, this may be a complicated problem. I believe I have an approach worked out, though it's a bit in depth as well.

There's a chance we can do it more simply, similar to how we have been. The MSFT engineer who made the changes isn't sure it will be that easy.

One quick thing that would help to investigate that angle — if you want to see if you can get TS v5 to build without tree shaking and send me the compiled typescript.js and tsc.js files, I will be able to take a look and see if the simple approach will work.

I do have one other person who's interested in helping with support and the rewrite. If you're interested, I can send a slack invite.

[AlCalzone]

If you're interested, I can send a slack invite.

You can send me one. I'm relying heavily on ts-patch and should be able to spare some time to help out.

[moshest]

@nonara I think I manage to build Typescript without tree shaking but the differences aren't big so maybe I only manage to do so partially:

• tsc.js - 5.7MB instead of 5.8MB
• typescript.js - same size 8.2MB

What I did is update the file Herebyfile.mjs:

+ treeShaking: false,
- treeShaking: taskOptions.treeShaking,

And built it using the command:

npm run build:compiler

I hope it helps.

[nonara]

@moshest Thank you. I sent you a slack invite if you'd like to join. @AlCalzone built it with shaking disabled and sent the files on slack.

Good news — I managed to get it to augment the new tsc. It runs properly and seem to be good. We need to test to be sure. Next steps are easier. Feel free to accept the invite and join in.

[sunrabbit123]

How long until ts-patch supports V5? If it's still a ways off, I would like to contribute as well.

Could you share the code blocks for the tests that need to pass and the work that needs to be done?

In ttsc, we hacked createProgram.

[nonara]

How long until ts-patch supports V5? If it's still a ways off, I would like to contribute as well.

Thank you. It's almost there. We've overcome the large hurdle. Will update in this thread shortly.

[nonara]

Hi all. I've updated the body of the original post with the latest update. We're close to release.

[TankOs]

@nonara I really don't want to bug you, but any info on the release? We're currently thinking about downgrading from TS 5 to 4, or just waiting for a couple of days until your new release hits the road. 🙂

[nonara]

@TankOs I appreciate that! I know everyone is ready, and I'm with you on that. I finished everything for the beta last night, and I'm working on some high level e2e tests right now so I can push out a beta. Shooting for today, but it definitely won't be long now.

[nonara]

Hi all. We have a beta ready that works for both ts-patch and ttypescript projects! 🔥

I'd really appreciate you trying it out and letting me know if it works for you.

For now, you can use yarn add -D ts-patch@v3-beta. I will keep that tag up to date with the latest beta

• If it works in your ts-patch based project, please leave a 🚀 emoji on this message
• If it works in your ttypescript based project, please leave a 🎉 emoji
• If anything doesn't work, please leave a comment

Please note that this is an early release, intended to get everyone going. Everything should work, but I will be doing some more tuning and adding more comprehensive tests over the coming days.

Thank you for helping to beta test!

ttypescript migration

If you want to try with a ttypescript project, you can use:

• tspc to compile (instead of ttsc)
• { 'compiler': 'ts-patch/compiler' } in a config (instead of { 'compiler': 'ttypescript' })

Or with ts-node, etc. via cli arg:

--compiler ts-patch/compiler

Helping out

If anyone would like to help build tests, please leave a comment on the v3-beta PR. I'm planning to organize how to approach those next week and would appreciate any help available.