-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add errors/warning where we're sure that an error could be #10
Comments
Needs to revert changes for #5 and warn about using |
…perties in it We can safely use `in` operator with "public" (or "external") API, but not with internal one. - See bc0face - See timocov/ts-transformer-properties-rename#10
Depends on microsoft/TypeScript#36733 |
Terser supports mangling properties defined in defineProperty so it's irrelevant. /cc @artfiedler |
Nooooooo….. Lol I believe those docs are out of date, I had verified terser worked, I had the latest version of terser
From: Evgeniy Timokhov
Sent: Saturday, July 4, 2020 5:21 AM
To: timocov/ts-transformer-properties-rename
Cc: Arthur Fiedler; Mention
Subject: Re: [timocov/ts-transformer-properties-rename] Add errors/warningwhere we're sure that an error could be (#10)
Quite possible that we need to revert changes from dc11196 and warn about defining properties because at least terser doesn't support properties renaming defined in Object.defineProperty. From the docs https://terser.org/docs/cli-usage#cli-mangling-property-names-mangle-props:
Avoid calling functions like defineProperty or hasOwnProperty, because they refer to object properties using strings and will break your code if you don't know what you are doing.
/cc @artfiedler
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Yep, I've tested it after posting my comment and it works fine. |
Related to terser/terser#748 |
This is merely to warn people who don't understand the limitations. I got tons of issues which assumed Terser did full flow analysis (which it doesn't). Ideally I would love property mangle to work more safely, and using typescript typing information to achieve this is a great idea! |
Related to #8 (comment)
The text was updated successfully, but these errors were encountered: