-
Notifications
You must be signed in to change notification settings - Fork 23
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
Migrate to Vite #352
Migrate to Vite #352
Conversation
46b388f
to
5d92a53
Compare
Upgrade major dependencies
a60f840
to
513b806
Compare
packages/extension/src/components/organisms/TransactionListing/format.util.ts
Show resolved
Hide resolved
c463dd8
to
cfed13e
Compare
"stream-browserify": "^3.0.0", | ||
"web-vitals": "^3.5.1", | ||
"xrpl": "^3.0.0", | ||
"xrpl-accountlib": "^3.2.9" | ||
}, | ||
"devDependencies": { | ||
"@gemwallet/constants": "*", | ||
"@gemwallet/eslint-config": "*", |
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.
You are pulling our eslint configuration, though we can see in the dev dependencies that you are using the dependencies from vite.js as you require another version of eslint.
We have two solutions here:
- We use the configuration from vite.js for the linter on the extension and the package @gemwallet/eslint-config for the API
- We update our configuration within @gemwallet/eslint-config to match vite and override it, and we make use of it within the extension.
We can also do this in another MR to don't add more change as this is not blocker.
What do you think?
4dd6d75
to
6adb39f
Compare
No description provided.