Is this project deprecated?

[vinyll]

I am about to write an app based on this project. It should be resilient.

is this ts-force lib usable, maintained and ok for production?

[ChuckJonas]

I'm not actively adding new features, but the library is production stable and I will continue with patches and welcome community support (I'm working on closing the open PR's just have been extremely busy lately).

[vinyll]

Right, it makes sense. It seems to be setup for version 50 by default. Any experience with more recent versions (v58)?

I notice your project was forked and continued by @vacasaoss, however I havent checked if the work done was specific or generic enough to be considered.

[ChuckJonas]

@vinyll Salesforce is pretty good about introducing breaking changes to the foundational API contract so really I wouldn't expect there to be any issues.

I just updated locally to v58 and ran all the tests (which are actually fairly comprehensive) and everything passes as expected. I'll probably go ahead and publish with default version on v58.

Now that I just released @colinfindlay-nz changes, the differences don't seem to be very substantial between the two. Guessing, they just got tied of waiting on me to release the updates.

Maybe @colinfindlay-nz could speak to his experience with ts-force in terms of "production" readiness

[colinfindlay-nz]

We've been running ts-force under pretty high loads constantly for more than a year. It's been stable and reliable, but our use case is reasonably simple.

We do see the odd connectivity issue, but in most cases it's been pinned down to AWS or Salesforce related problems.

The vacasaoss fork is there so we can apply any critical patches in a timely manner - if we added new features (no plans!), they would be contributed back.