Skip to content
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

v1 » v2 migration #14

Closed
Tracked by #12
threepointone opened this issue Nov 16, 2021 · 1 comment
Closed
Tracked by #12

v1 » v2 migration #14

threepointone opened this issue Nov 16, 2021 · 1 comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@threepointone
Copy link
Contributor

This issue is for tracking details on how to migrate a project from v1 to v2. Roughly, the difference between the features that look the same, what features are deprecated and how to replace their functionality, and maybe how to take advantage of newer features.
@threepointone threepointone added documentation Improvements or additions to documentation enhancement New feature or request labels Nov 16, 2021
@threepointone threepointone mentioned this issue Nov 16, 2021
Closed
27 tasks
@petebacondarwin petebacondarwin moved this to Non-blocking in workers-sdk Jan 25, 2022
@petebacondarwin petebacondarwin added this to the Wrangler 2.0 milestone Feb 1, 2022
@petebacondarwin petebacondarwin modified the milestones: 2.0, 2.0.x May 11, 2022
@petebacondarwin
Copy link
Contributor

Closing as this issue has nothing specifically actionable and we have pretty much covered migration from W1.
Any specific migration concerns should be captured in a new issue.

Repository owner moved this from Should-have to Done in workers-sdk May 12, 2022
Huntemall pushed a commit to snowcittysolutions/workers-sdk-dev that referenced this issue Oct 3, 2023
@threepointone
feat(tail): add initial support for tail (cloudflare#14)
0641a8d 
* feat(tail): add initial support for tail

* cleanups

- removed the potential react component
- removed the heartbeat logic
- read account id and name from config
- sunil pai's annoying habit of defining top level function with the function keyword

Co-authored-by: Sunil Pai <spai@cloudflare.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@petebacondarwin @threepointone