Skip to content

Replace demo folder with StackBlitz #704

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Jan 20, 2025
Merged

Replace demo folder with StackBlitz #704

merged 3 commits into from
Jan 20, 2025

Conversation

@Murderlon
Copy link
Member

Closes #547
Closes #343

@Murderlon Murderlon self-assigned this Jan 20, 2025
@changeset-bot
Copy link

changeset-bot bot commented Jan 20, 2025 •
edited
Loading

⚠️ No Changeset found

Latest commit: 7913282

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security
Copy link

socket-security bot commented Jan 20, 2025 •
edited
Loading

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: npm/cross-env@7.0.3, npm/tus-js-client@2.3.2

View full report↗︎

@Murderlon Murderlon merged commit 3b5718b into main Jan 20, 2025
3 checks passed
@Murderlon Murderlon deleted the demo branch January 20, 2025 14:01
Murderlon added a commit to netdown/tus-node-server that referenced this pull request Jan 20, 2025
@Murderlon
Merge branch 'main' into feat-gcs-locker
dec6d39 
* main: (59 commits)
  Replace demo folder with StackBlitz (tus#704)
  @tus/gcs-store: correctly pass content type (tus#702)
  @tus/s3-store: fix zero byte files (tus#700)
  Update package-lock.json
  [ci] release (tus#696)
  fix: handling consistent cancellation across stream and locks (tus#699)
  @tus/s3-store: Change private modifier into protected (tus#698)
  Create funding-manifest-urls
  Bump @aws-sdk/client-s3 from 3.703.0 to 3.717.0 (tus#695)
  Bump mocha from 10.4.0 to 11.0.1 (tus#693)
  Bump @biomejs/biome from 1.9.2 to 1.9.4 (tus#694)
  [ci] release (tus#690)
  Bump @aws-sdk/client-s3 from 3.701.0 to 3.703.0 (tus#685)
  @tus/s3-store: fix part number increment (tus#689)
  Revert "Bump rimraf from 3.0.2 to 6.0.1 (tus#681)"
  Bump @aws-sdk/client-s3 from 3.682.0 to 3.701.0 (tus#683)
  Bump @changesets/cli from 2.27.9 to 2.27.10 (tus#682)
  Bump rimraf from 3.0.2 to 6.0.1 (tus#681)
  Bump @types/node from 20.11.5 to 22.10.1 (tus#679)
  Ignore JSON for Biome formatting
  ...
@mitjap
Copy link
Collaborator

mitjap commented Feb 10, 2025

I miss this demo setup. This was great way to debug and test various datastores, configurations, isolate issues, reproduce bugs, ...

Maybe I'm not familiar with all tools used to run/debug this project. How do you run tus-node-server to debug with real client request and real datastore?

@Murderlon
Copy link
Member Author

I personally never used it for that I always start by writing a test if something is wrong which is great because then we also have that going forward.

If you think it's important, feel free to create an issue for a new dev setup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@Murderlon Murderlon

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Demo for GCS incorrectly uses GCSDataStore Upgrade tus-js-client to 3.x and rewrite the demo

2 participants

@Murderlon @mitjap