Skip to content

feat!: ist winddown#175

Merged
samsiegart merged 3 commits into
mainfrom
ist-winddown
May 28, 2025
Merged

feat!: ist winddown#175
samsiegart merged 3 commits into
mainfrom
ist-winddown

Conversation

@samsiegart

@samsiegart samsiegart commented May 28, 2025

Copy link
Copy Markdown
Collaborator

Changes the provision smart wallet notice / onboard ist modal to support bld as well when it's set as the swingset fee.

Upgrades @agoric/web-components which now uses BLD only as the fee token for the wallet connection.

Removes the "tsc" step in build because vite already compiles it and I got an error in node_modules when upgrading @agoric/web-components https://gist.github.com/samsiegart/7794b51ef6875a14fc5521a53bf9fdb0

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented May 28, 2025

Copy link
Copy Markdown

Deploying dapp-psm with  Cloudflare Pages  Cloudflare Pages

Latest commit: 77e9ee8
Status: ✅  Deploy successful!
Preview URL: https://87e75c97.dapp-psm.pages.dev
Branch Preview URL: https://ist-winddown.dapp-psm.pages.dev

View logs

Comment thread package.json
"scripts": {
"dev": "vite",
"build": "tsc && vite build",
"build": "vite build",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Removes the "tsc" step in build because vite already compiles it and I got an error in node_modules when upgrading @agoric/web-components https://gist.github.com/samsiegart/7794b51ef6875a14fc5521a53bf9fdb0

Thanks for explaining this. In the other PR I asked for tsc to be in lint. I won't ask that here. I thought of asking that the reason for omission be mentioned in the README but maybe by the time someone tries to add tsc back it won't have problems. If it does they won't have wasted much time finding out.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I added a yarn lint:types with a warning. My standpoint is that this would take some effort to debug here and in Agoric/dapp-inter#401 and these apps are going to be shut down soon anyway

({ key }: { key: string }) => key === 'feeUnit'
)?.beans;
const feeUnitName = params.params?.feeUnitPrice[0]?.denom;
assert(feeUnit);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

consider an error message. also they all need to be present (if they aren't the BigInt will make 0n)

Suggested change
assert(feeUnit);
assert(beansPerSmartWallet && feeUnit && feeUnitName, 'missing fee params');

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Done

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert (click for details)
Warn High
node-forge@1.3.1 has a License Policy Violation.

License: GPL-2.0 (package/LICENSE)

From: yarn.locknpm/node-forge@1.3.1

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-forge@1.3.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@samsiegart samsiegart requested a review from turadg May 28, 2025 17:32
@samsiegart samsiegart merged commit 76f7e26 into main May 28, 2025
4 checks passed
@samsiegart samsiegart deleted the ist-winddown branch May 28, 2025 17:39
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.

2 participants