Hey folks! We have some exciting news to share.

After talking with @stomita , we've agreed the Salesforce CLI team will help maintain jsforce!
jsforce is a core component of the Salesforce CLI, Salesforce Extensions for VSCode, DevOps Center and a bunch of other Salesforce tools and we hope we can help Shinichi keep the project alive while delivering new features.

We know there hasn't been much activity triaging issues and PRs except for a few specific bug fixes/features, you can expect us to be more active in the repo while we work towards the v3 GA.

Dropping support for old node and browsers

jsforce v2 has been in beta for almost 3 years supporting node >= v8 and some old browsers (polyfills).
To avoid breaking projects already using v2 we plan to skip and go straight to v3 for the GA, requiring node >= 18 (current LTS) and modern browsers.

Browser usage

While we don't use jsforce in browsers (CLI and others run via node), we are committed to keep jsforce an isomorphic library.
We've already improved our CI test setup to run browser tests on latest Chrome, updated webpack/babel deps and fixed some flaky tests to ensure a safe path while we finish the last bits of work.

We will also remove the edge versions (/dist) these were already outdated when using a CDN. If you wish to continue using them, you can continue using the CDN versions here and the jsforce npm package includes these so they are available in modern CDNs that serve from npm.

Remaining work

• Migration guide v1 → v3
• Triage issues and PRs targeting v2 branch
• Documentation equivalent to the current jsforce.github.io (http://jsforce.github.io/). PR ci: use typedoc for docs #1362
• Drop support for old node and browsers https://github.com/jsforce/jsforce/pull/1369/files#r1363986316
• node-only release, see: node-only release #1374
• Annotations to the code for API references.
• Run CLI tests on PRs to catch regressions PR ci: add Salesforce CLI NUTs to the test matrix #1359
• Run node test on Windows
• Automate TS typegen (followup issue)