sanity-plugin-table migration to V3

[davydog187]

Hello! I'm looking for guidance on publishing a fork of the popular Sanity Table Plugin that I've migrated to Sanity V3.

Background

Unfortunately, the plugin has has not been maintained for some time, although a fork did spend some time merging in bugfixes. My company makes heavy use of this table, so we plan to take stewardship over the table and add additional features, such as PortableText support. I have created my own fork that grabs these bugfixes, and then begun the migration to Sanity v3.

Migration Work

• My fork with the V3 migration
• PR migrating to V3

Future Plans

• Support PortableText more generally in table cells

Related Discussion

• V3 enabled table plugins

Questions

I want to publish a V3 version to npm and get the official Sanity page updated once the migration is complete. My concern is regarding how to publish with minimal confusion to the community

1. How should I handle publishing to npm given that the original already exists under the name sanity-plugin-table?
2. Should I diverge the plugin name from table to something else? I think it would be best to keep the same. (The other fork renamed it to another-table which I was not a fan of).
3. How should we handle updating the official Sanity page?

I'm happy to do whatever is in the best interest of the community, but since we are maintaining this fork, I would prefer to keep it under our control.

[davydog187]

Also paging @rdunk and @MathisBullinger. Ideally we can find a solution where we get maintainer access to the canonical repo and we can further it there.

[snorrees]

@sanity/table 1.0.0 for v3 is now out.
This version is officially under Sanity.io stewardship for v3 moving forward.

Thanks a lot for this work @davydog187 ! All contributors original and otherwise should be credited in the MIT license and readme.
Let me know you anyone are left out.