fix: add treeshakable to useProgress

[mayank1513]

This will ensure that only one instance of useProgess is created. For more info please see https://github.com/react18-tools/treeshakable/ and https://treeshakable.vercel.app/

Why

Enhancement: allow importing from the component files, e.g., ./web/Loader to avoid importing unnecessary code.

What

Wrapped store creation inside treeshakable

Checklist

• Documentation updated (example)
• Storybook entry added (example)
• Ready to be merged

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
drei	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 4, 2024 5:09am

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[mayank1513]

Not updating KeyboardControls as the store is created within the component and passed to children using context. Updating this will require breaking changes.

[github-actions]

Thank you for your work on this pull request! We’re marking this PR as stale to encourage a final push to bring it across the finish line.

Any update, comment, or change to the PR will automatically remove the stale label so it stays active in our workflow.

If you need any help, don’t hesitate to connect with us on Discord for feedback and support. This PR will close automatically soon if there’s no further activity, but we’re here to help if you’re interested in getting it merged. Thank you for your contribution!

[github-actions]

We’re closing this pull request to help manage our workload and focus on active contributions. We really appreciate the effort you put into this, and we’d be happy to revisit it anytime you’re ready.

Please feel free to re-open this PR or reach out on Discord if you’d like to continue — our community is always here to support you. Thanks again for your contribution and for helping us stay organized!