Skip to content
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

Deploy to base #35

Merged
merged 6 commits into from
Apr 10, 2024
Merged

Deploy to base #35

merged 6 commits into from
Apr 10, 2024

Conversation

tuler
Copy link
Member

@tuler tuler commented Apr 9, 2024

Deploy contracts to base network.

@tuler tuler requested a review from guidanoli April 9, 2024 18:43
@coveralls
Copy link

coveralls commented Apr 9, 2024

Pull Request Test Coverage Report for Build 8631128767

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 94.24%

Totals Coverage Status
Change from base Build 7214077584: 0.0%
Covered Lines: 274
Relevant Lines: 290

💛 - Coveralls

@guidanoli
Copy link
Contributor

guidanoli commented Apr 10, 2024

The pnpm run prettier command on packages/contracts is not working.

No parser could be inferred for file "...".

Adding the following line to the .prettierrc.json file seems to fix the problem.

diff --git a/packages/contracts/.prettierrc.json b/packages/contracts/.prettierrc.json
index 100e63c..cca0824 100644
--- a/packages/contracts/.prettierrc.json
+++ b/packages/contracts/.prettierrc.json
@@ -1,5 +1,6 @@
 {
     "tabWidth": 4,
+    "plugins": ["prettier-plugin-solidity"],
     "overrides": [
         {
             "files": "*.sol",

@guidanoli
Copy link
Contributor

I was not able to figure out the tsc error when we migrated from yarn to pnpm though...

@guidanoli
Copy link
Contributor

Setting skipLibCheck to true on tsconfig.json worked, but I'm not sure whether it's safe to go down this path.

@tuler
Copy link
Member Author

tuler commented Apr 10, 2024

skipLibCheck

I think it's a fair compromise for now.

@guidanoli
Copy link
Contributor

guidanoli commented Apr 10, 2024

It appears that even big projects that depend on viem@^2 such as OneKey use this configuration.

@guidanoli
Copy link
Contributor

There are references to Yarn in the README

@tuler
Copy link
Member Author

tuler commented Apr 10, 2024

It appears that even big projects that depend on viem@^2 such as OneKey use this configuration.

It should definitely not be needed, but I would't worry in this case

@guidanoli
Copy link
Contributor

It should definitely not be needed, but I would worry in this case

I agree. I wonder, though, if this issue can be fixed later.

README.md Show resolved Hide resolved
Copy link
Contributor

@guidanoli guidanoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Optionally, I would sort the entries in the tsconfig.json.

@tuler tuler merged commit e33631b into main Apr 10, 2024
2 checks passed
@tuler tuler deleted the feature/base-deploy branch April 10, 2024 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants