Replies: 2 comments
-
Beta Was this translation helpful? Give feedback.
0 replies
-
This would be a break change for browsers natively support class field, but since tsc doesn't have |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Concerning recent issues of #3317 and #3389 which requires [[Define]] for class fields in typescript, here is my proposed steps to fix:
classes
fix(ecma/transform/compat): constructor #3505 so we can reuse babel testsclasses
feat(es/transforms/compat): loose mode for classes #3474class_properties
so we can reuse babel tests fix(ecma/transform/compat): private and new.target in class properties #3594 mod(es): change definition of optional chain #3645 fix(ecma/transform/compat): private properties cannot be initialized twice #3665 fix(ecma/transform/compat): private getter/setter #3695class_properties
feat(es/transforms/compat): loose mode for class_properties #3722use_define_for_class_field
inconfig.jsc
. If this is set to true, automatically setset_public_class_fields
to true, feat: unify class properties transform in ts and js #3766Beta Was this translation helpful? Give feedback.
All reactions