-
Notifications
You must be signed in to change notification settings - Fork 22
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.
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
refactor(cloudflare): make node:util/types
a nodejs_compat
module
#329
Conversation
8809b04
to
4bc9c29
Compare
node:util/types
a nodejs_compat
module
What workerd version this PR depends on? We can not pull this code in wrangler before wrangler pulls the required version of workerd. More generally I think we should use whatever workerd version is bundled with wrangler for the tests. Having a different version is a recipe for troubles. @anonrig that's probably something we need to discuss internally. |
I think we discussed about it to split wrangler preset/versioning so we can test and upgrade unenv according to the latest workerd release. |
Are you referring to #262? I think the problem we need to solve for wrangler is how to make sure I'm unsure if creating a wrangler preset is the best way to solve this - hopefully this repo is never aware about wrangler. What I mean is that unenv patches should depend on workerd version, not wrangler version. When we have a way to do that then wrangler will pick the unenv version matching the workerd version it bundles. |
|
4bc9c29
to
811a7b6
Compare
This change was released almost 4 months ago - cloudflare/workerd@799dfbe. The change is first introduced in v1.20240614.0. @vicb |
@vicb I agree. In the long term, we should match those 2 version. Right now, wrangler |
Maybe we should have 2 tags for workerd: "prod" and "wrangler" and test both versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you ❤️
Feel free to merge when/if prod version of workerd shipped this
All methods in
util/types
are implemented. We can remove the hybrid module status fromnode:util/types