use watch dir for cloudflare workers template
there's a lot of issues with the cloudflareDevProxyVitePlugin when it comes to bindings and the dev server. this commit uses watch_dir instead of the plugin. To make bindings easier to work with.
Closes: #
- [ ] Docs
- [ ] Tests
Testing Strategy:
⚠️ No Changeset found
Latest commit: eb919814549b631f0935e47682d89dd8f2ddd924
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
Thank you for opening this pull request, and our apologies we haven't gotten around to it yet!
With the release of React Router v7 we are sun-setting continued development/maintenance on Remix v2. If you have not already upgraded to React Router v7, we recommend you do so. We've tried to make the upgrade process as smooth as possible with our Future Flags. We are now in the process of cleaning up outdated issues and pull requests to improve the overall hygiene of our repositories.
We plan to continue to address 2 types of issues in Remix v2:
- Bugs that pose security concerns
- Bugs that prevent upgrading to React Router v7
If you believe this pull request meets one of those criteria, please respond or create a new pull request so it pops up on our radar (since github notifications may get lost in the noise 😕).
For all other issues/changes, ongoing maintenance will be happening in React Router v7, so:
- If this is a bug fix, please reopen against React Router v7
- If this is a new feature, please open a new Proposal Discussion in React Router, and if it gets enough community support it can be considered for implementation
If you have any questions you can always reach out on Discord. Thanks again for providing feedback and helping us make our framework even better!