I touch upon this a little in the epilogue section https://sunilpai.dev/posts/seven-ways/#epilogue-ok-but-doesn... I was thinking what work there really is for "juniors" in this new future, and I suspect the answer then that their "job" is to develop the understanding of the codebase, approaching changes from the edges, and learning how to introduce new changes. (very similar to how people would onboard to a codebase pre-llms: by writing tests, doing smaller changes, poking about the code by adding console statements, etc). The good news is that the coding agent is a very good tool to do that as well. I plan on writing more about this soon.
It is indeed excellent. y-partykit is a library for building a backend on PartyKit, but PartyKit itself isn't tied to Y.js; you can deploy any tech you want on to it.
Hello! I'm on the team that implemented this. I'll be writing a longer post on the design considerations and implementation details, but roughly - rust wasn't a good case for something that was mostly held back by i/o to the edge; further, the actual cpu/mem intensive part was handed off to webpack which was written in javascript. So wrangler v2 flips that design around, using typescript for the outer shell, which makes it easier for our users and community to contribute to the tool, and esbuild for the core part of parsing/bundling code (we may switch esbuild to a rust based bundler like swc in the future).
Yeah agreed, this is pretty ad-hoc right now, smeared across different commands and config. We're working on a better solution, will share more details when we have something. Thank you for your feedback!
Could you share more detail about your usecase? What kind of checks are you looking for? I'd be happy to have a look at that (and presumably if we could do it before it gets uploaded, that would be great)
Fun fact, that post 3 months ago was what got us folks at cloudflare in touch with the author, who then interned with us for 2 months (today was his last day!)
Errors - We're getting better at this. You can now use `--inspect` and use chrome devtools which should log proper exceptions (details to setup https://blog.cloudflare.com/profiling-your-workers-with-wran...)
Console.logs - same as above! Real devtools, interactive and everything.
Timeouts and crashes - This should be better now, timeouts and sessions expires now transparently heal and restart, so you shouldn't face errors (Please file an issue if you see different!)
Overall we're working hard on making this experience better, please feel free to file issues if you see anything that's not expected. Thank you!
I've faced this too, where you'll save, then hit refresh, and it show the previous version; despite the fact that we "know" that the code is changed. SO we should be able to queue requests when we have a new version uploading (and of course, make the whole thing faster). Thanks for your feedback!
This is amazing feedback, thank you very much! I'm going to work on each of these; but quickly - we definitely shouldn't have something that works in `wrangler dev` but not in the platform, and we should warn/error on that, our docs shouldn't have examples that don't work :facepalm:, and we should be spec compliant where we can. Thank you so much!
I'm so sorry you had to deal with that. We're working on removing a lot of friction from the onboarding process, and making it easier to introspect what everything's doing. Thank you for your feedback!
We also don't have a lockin to webpack anymore (you can choose custom builds with the "javascript" type, which I admit is a little confusing). We're going to move away from even this dependency and make everything much faster and lighter, stay tuned.