-
Notifications
You must be signed in to change notification settings - Fork 0
fix: web3 import and ts compiler config #212
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
Conversation
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ |
tsconfig.json
Outdated
"sourceMap": true, | ||
"strict": true, | ||
"target": "ES2017" | ||
"target": "ESNext" |
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.
Why is changing compile target from es2017 to esnext done here? How is it "better"?
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.
@legobeat its to target the latest supported by our TypeScript version. I need to explain better the PR description, but with "better" i was not referring to this change in particular, but the previous configuration was also including test files on the dist
, so better in terms of "we are packaging only what we need"
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.
I guess I feel a bit hesitant about this one, as well as the lib
removal on :7
, timing-wise... The rest looks straightforward enough, but there's also a lot going on here.
Was thinking perhaps the changes in this PR can be broken into more than one PR, so they can be more easily reviewed and merged independently.
But this may be more straightforward to someone more familiar with that context!
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.
in this very particular case, its really straightforward. lib
was removed because we dont need definitions for browser environment (since this is only used on mobile), and since our target changed, the ES2020 inclusion in lib, no longer makes sense.
i merged your suggestion to go from ESNext to ES2020 to move slower in terms of target
if its worth mentioning, i have also run integration tests on top of a mobile build using this new set of options and everything works as expected
…ndabot/npm_and_yarn/main/metamask/controller-utils-9.1.0
Co-authored-by: legobeat <109787230+legobeat@users.noreply.github.com>
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.
LGTM!
This PR fixes:
dist
@metamask/controller-utils
updates. Aims to remove BigNumber usage in a future version