Road to 1.0.0

This is the mother issue for the road to 1.0.0, which marks the first semver stable release for tus-node-server.

Progress on this release happens on the 1.x branch. From now on we should carefully land things in master, as merge conflicts between the same .js and .ts files are hard to resolve. Ideally we only work on 1.x now, except for critical bugs.

Planned

#158 + new modern tooling (@Murderlon)
Implement proxy support. Take tusd proxy support as inspiration (@Murderlon)
Rename getOffset (PR)
Rename File model to Upload and rename keys.
https://github.com/tus/tus-node-server/issues/319
https://github.com/tus/tus-node-server/issues/336
https://github.com/tus/tus-node-server/issues/300
Return 413 Request Entity Too Large when the client sends more data than reported with Upload-Length (PR)
S3: support chunks under 5 MB.
S3: implement buffering to prevent hitting the 10K parts limit. If we send a 500 GB file, we need to make sure we set the part size to around 52 MB in order to prevent hitting the 10K parts limit
#61
Rewrite the README (@Murderlon)
Change master to main

Up for debate

Rethink ConfigStore (issue)
S3: add termination extension
GCS: add termination extension

Opinions welcome!

Issue Analytics

State:
Created a year ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

Murderloncommented, Oct 10, 2022

It’s not that it is too much work but this major version would be the moment to switch. Because people would have to check what happened in the breaking change and find out that stores are now separate install and while they’re add it they might as well reinstall the server. It would be less obvious to suddenly stop updating a deprecated package in a non-major, and waiting till 2.0.0 is a bit of a stretch and a mismatch with the already separated packages in 1.0.0.

I’ve thought about it more and I think we should switch to the @tus scope in 1.0.0 for all tus packages in the JS ecosystem (so also tus-js-client). Having a scope further signals official packages and prevents awkward naming.

1reaction

Murderloncommented, Oct 5, 2022

This roadmap looks good to me! Do you need any specific help from my side as I am assigned as well?

No I just added you for feedback and occasional questions/support 😃

Top Results From Across the Web

The Road To 1.0.0 - Origin Realms

Adventure Worlds & Dungeons ... Alongside leveling and skill growth systems, we've put a large emphasis on our dungeon experience with this update ......

Dungeons - Origin Realms Wiki - Fandom

Considered the Core of Adventure Worlds, dungeons in Origin Realms aims to be one of the most polished and rich dungeon experiences yet...

Road to 1.0.0 Milestone - GitHub

Road to 1.0.0 · Create script to generate the custom theme area/library Related to all activities around Library package enhancement New feature or...

The Road to 1.0 – React Blog

It exists as a way to pass values through a tree without having to use props at every single point. We've seen this...

Road to 1.0 - July 2021 Development Update

To provide more insight into how multiplayer is developing, today we are pushing out our first **monthly multiplayer development update** to ...