尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
• Fork the original repo into your GitHub account
• Clone the forked repo from your GitHub account to your local machine
• Set origin to your fork. This is where you push your changes to. This is done automatically by the step above.
• Set upstream to original repo.
• Optional: Create a .env file in the repo root, copy .env.example, and replace values with your own keys. Client-readable values must use the NEXT_PUBLIC_ prefix; server-only secrets must stay unprefixed.
• Optional: Install Husky for pre-commit scripts.檢視完整 README ↗Fork the original repo into your GitHub account
Clone the forked repo from your GitHub account to your local machine
git clone https://github.com/<your-gh>/yearn.fi.git
Set origin to your fork. This is where you push your changes to. This is done automatically by the step above.
git remote add origin https://github.com/<your-gh>/yearn.fi
Set upstream to original repo.
git remote add upstream https://github.com/yearn/yearn.fi.git
Optional: Create a .env file in the repo root, copy .env.example, and replace values with your own keys. Client-readable values must use the NEXT_PUBLIC_ prefix; server-only secrets must stay unprefixed.
cp apps/yearn/.env.example .env
Optional: Install Husky for pre-commit scripts.
bun add --dev husky
Use Node.js 22.22.1+ (22.x), as required by lint-staged 17, and Bun 1.4.2 or newer.
The type-check and watch scripts invoke TypeScript 7 directly because the TypeScript 6 compatibility package used by boundary checks can also provide the tsc command.
bun install from the repository root.bun run dev (or bun run dev:yearn) for Yearn at http://localhost:3000.bun run dev:ybold for yBOLD at http://localhost:3002.Both apps consume the private @yearn/vault-widget source package from this
workspace. No registry publish is required.
To disable Enso routing for specific vaults, edit:
apps/yearn/src/components/pages/vaults/constants/ensoDisabledVaults.ts
Add vault addresses under their chain ID:
const ENSO_DISABLED_VAULTS_BY_CHAIN: Partial<Record<number, readonly Address[]>> = {
1: [
'0x1111111111111111111111111111111111111111'
],
42161: [
'0x2222222222222222222222222222222222222222',
'0x3333333333333333333333333333333333333333'
]
}
Notes:
1, 10, 137, 42161, etc.).Create a new local branch from upstream/main for each PR that you will submit
git fetch
git checkout -b <your branch name> upstream/main
Commit your changes as you work
git add .
git commit -S -m "message"
Commits are squashed when PR is merged so rebasing is optional
When ready to push
git fetch
git merge upstream/main
git push origin <branch-name>
Pull requests and then click on New pull requestcompare across forkscompare: and select branch that you want to create a pull request for then click on create pull request