Initialize cli

.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/[email protected]/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "cli",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

.github/workflows/release.yml

@@ -0,0 +1,33 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - cli
+
+concurrency: ${{ github.workflow }}-${{ github.ref }}
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repo
+        uses: actions/checkout@v3
+
+      - name: Setup Node.js 16.x
+        uses: actions/setup-node@v3
+        with:
+          node-version: 16.x
+
+      - name: Install Dependencies
+        run: yarn
+
+      - name: Create Release Pull Request or Publish to npm
+        id: changesets
+        uses: changesets/action@v1
+        with:
+          publish: yarn changeset:release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

.gitignore

@@ -0,0 +1,15 @@
+/dist
+
+# Dependency directories
+node_modules/
+
+# yarn
+.yarn/*
+!.yarn/patches
+!.yarn/plugins
+!.yarn/releases
+!.yarn/sdks
+!.yarn/versions
+
+# macos files
+.DS_Store

.yarnrc

@@ -0,0 +1 @@
+--save-exact true

.yarnrc.yml

@@ -0,0 +1,5 @@
+enableColors: true
+
+nodeLinker: node-modules
+
+yarnPath: .yarn/releases/yarn-3.5.0.cjs

CHANGELOG.md

@@ -0,0 +1,201 @@
+# create-eth
+
+## 0.0.35
+
+### Patch Changes
+
+- Yarn flatten (#745, 62553fd)
+- Add format with prettier task (b03c011)
+- Fix local next build (#749)
+- Fix emit event value in contract (#765, 833d09b)
+- Fix useScaffoldContractWrite so it properly throws errors (#758)
+- Fix vercel deployment mismatch (#757)
+- Remove extra notifications when using useTransactor (#766)
+- Ignore JetBrains IDE settings file (#732)
+- Fix hardhat lint errors (ac1d2ac)
+
+## 0.0.34
+
+### Patch Changes
+
+- 092f2ad: 1. basic example to show connected address (#721) 2. Standardize displaying of address and follow ERC-55 (#734) 3. fix contract balance hot reload balance issue (#739) 4. Fix cursor stealing & display loading for AddressInput (#738) 5. Fix blockexplorer code tab (#741) 6. Match link name with actual tab name for Debug Contracts (#743)
+
+## 0.0.33
+
+### Patch Changes
+
+- Feat: Better complex struct inputs (#702)
+- improve debug struct UI (#726)
+- use next-themes to handle theme and update usehooks-ts (#707)
+- up rainbowkit version to 1.3.5 (#719)
+- Use arbitrumSepolia instead of Goerli (#716)
+- Add Optimism Sepolia config (#711)
+- Update screenshot example on Readme (#705)
+- add use client to inputs barrel file (#699)
+- add baseSepolia in hardhat.config (#696)
+- removed "use client" from EtherInput, IntergerInput and AddessInput (#688)
+
+## 0.0.32
+
+### Patch Changes
+
+- App router migration (#535)
+- Update hardhat package plugins and add hardhat-verify (#637)
+- Update homepage file route and add Viem to README tech stack (#691)
+- Ethers v6 migration in hardhat (#692)
+
+## 0.0.31
+
+### Patch Changes
+
+- Track hardhat-deploy deployments, except localhost (#666)
+- feat: add external flag to external contracts (#647)
+- Remove `.github/ISSUE_TEMPLATE` and pull request template when using npx
+
+## 0.0.30
+
+### Patch Changes
+
+- Daisy UI: update to v4 (#656)
+- JSDoc cleanup (#665)
+- use default values for safeConnector (#667)
+- Typos (#668)
+- Remove custom Spinner component (#669)
+
+## 0.0.29
+
+### Patch Changes
+
+- Update wagmi to latest version: (#660)
+- Fix externalContracts object example code (#653)
+- Add question for installation method in template Issue (#651)
+
+## 0.0.28
+
+### Patch Changes
+
+- a9d873d: - Allow user to set his preference for AddressType in `abi.d.ts` (#630 & #641)
+  - Check for exact path segment for inheritedFunctions sources (#643)
+  - Fix displaying of custom solidity errors (#638)
+  - Check cause?.data on getParsedError (#649)
+
+## 0.0.27
+
+### Patch Changes
+
+- Feat/support multi chain (#615)
+- Add links to the docs for components and hooks (#620)
+- Fix useScaffoldEventHistory hook new events order (#622)
+- Add requiredFilters param to useScaffoldEventHistory hook (#621)
+- update wagmi, viem and rainbowkit versions (#626)
+- Refactor: types/interfaces (#627)
+
+## 0.0.26
+
+### Patch Changes
+
+- Show inherited functions in Debug page (when deploying with foundry)
+- Add disableMultiplyBy1e18 flag to IntegerInput component (#609)
+- Add pooling interval to EventHistory hook (#597)
+- Fix AbiFunctionReturnType removing [0] (#610)
+
+## 0.0.25
+
+### Patch Changes
+
+- 0135237: - Fix typos in comments (#596)
+  - Show inherited functions in Debug (when deploying with hardhat) (#564)
+
+## 0.0.24
+
+### Patch Changes
+
+- 06ba1eb: - remove chainId from useContractWrite (#584)
+  - Add copy to clipboard to TxReceipt (#590)
+  - Add event logs to transaction page (#591)
+  - deployedContracts & externalContracts (#592)
+
+## 0.0.23
+
+### Patch Changes
+
+- 30d9000:
+
+  1. Extract header menu links (#570)
+  2. Move Block Explorer to footer (#574)
+  3. Remove ExampleUI (pages, components, assets, content) (#578)
+  4. update wagmi, viem, rainbowkit (#580) 5. add zkSync, scroll & polygonZkEvm to foundry.toml ([88b4218](https://github.com/scaffold-eth/scaffold-eth-2/pull/582/commits/88b421860a5260d2c8ad4877adaf07c1d667f2b6))
+
+## 0.0.22
+
+### Patch Changes
+
+- 16f1a72: Tweak DaisyUI link (#560)
+
+  Improve ENS support (accept all TLDs) (#563)
+
+  fix: memo history events (#565)
+
+  update DEVELOPER-GUIDE.md with backmerge-main instructions
+
+## 0.0.21
+
+### Patch Changes
+
+- 9c967d9: 1. Fix RainbowKitCustomConnectButton dropdown styles (#500)
+
+  2. chore: footer missalignment & home page on small screens (#502)
+
+  3. Update and typescript version (#499)
+
+  4. fix: header links wrapping icons and text (#510)
+
+  5. Fix typos in useScaffoldContractWrite logs (#512)
+
+  6. fix: spelling in test file name (#522)
+
+  7. Add polygonZkEvm and polygonZkEvmTestnet (#309)
+
+  8. fix: eth price showing 0 on sepolia network (#532)
+
+  9. use websockets client in useFetchBlocks hooks (#529)
+
+  10. Move from react-blockies to blo (#538)
+
+  11. add Prettify type helper locally (#541)
+
+  12. update hardhat version (#546)
+
+  13. Add indexed args to events (#540)
+
+  14. add out of box compatibility with SAFE{Wallet} (#346)
+
+  15. remove parseEther from useScaffoldContractWrite (#548)
+
+  16. Add Scroll Sepolia testnet (#547)
+
+  17. use BuidlGuidl logo on footer (#551)
+
+  18. add types to even data in useScaffoldEventHistory (#553)
+
+  19. foundry: add chain id 31337 while forking chain (#531)
+
+## 0.0.20
+
+### Patch Changes
+
+- 32caee5: 1. Fix RainbowKitCustomConnectButton dropdown styles #500
+
+  2. chore: footer missalignment on mobile screens #502
+
+  3. Update and typescript version #499
+
+  4. add grid and grid-flow class to li manually #510
+
+  5. Fix typos in getScaffoldContractWrite lines 57 & 65 #512
+
+  6. fix: test file name #522
+
+  7. add support for `yarn verify --network networkName` in foundry similar to hardhat #489
+
+  8. updated the Git task title from "Initializing Git repository" => "Initializing Git repository and submodules" when the user selects foundry as an extension

CONTRIBUTING.md

@@ -0,0 +1,107 @@
+# Welcome to Scaffold-ETH 2 Contributing Guide
+
+Thank you for investing your time in contributing to Scaffold-ETH 2!
+
+This guide aims to provide an overview of the contribution workflow to help us make the contribution process effective for everyone involved.
+
+## About the Project
+
+Scaffold-ETH 2 is CLI tool to create a minimal repo providing builders with a starter kit to build decentralized applications on Ethereum.
+
+Read the [README](README.md) to get an overview of the project.
+
+### Vision
+
+The goal of Scaffold-ETH 2 is to provide the primary building blocks for a decentralized application.
+
+The repo can be forked to include integrations and more features.
+
+### Project Status
+
+The project is under active development.
+
+You can view the open Issues, follow the development process and contribute to the project.
+
+## Getting started
+
+You can contribute to this repo in many ways:
+
+- Solve open issues
+- Report bugs or feature requests
+- Improve the documentation
+
+Contributions are made via Issues and Pull Requests (PRs). A few general guidelines for contributions:
+
+- Search for existing Issues and PRs before creating your own.
+- Contributions should only fix/add the functionality in the issue OR address style issues, not both.
+- If you're running into an error, please give context. Explain what you're trying to do and how to reproduce the error.
+- Please use the same formatting in the code repository. You can configure your IDE to do it by using the prettier / linting config files included in each package.
+- If applicable, please edit the README.md file to reflect the changes.
+
+### Issues
+
+Issues should be used to report problems, request a new feature, or discuss potential changes before a PR is created.
+
+#### Solve an issue
+
+Scan through our [existing issues](https://github.com/scaffold-eth/scaffold-eth-2/issues) to find one that interests you.
+
+If a contributor is working on the issue, they will be assigned to the individual. If you find an issue to work on, you are welcome to assign it to yourself and open a PR with a fix for it.
+
+#### Create a new issue
+
+If a related issue doesn't exist, you can open a new issue.
+
+Some tips to follow when you are creating an issue:
+
+- Provide as much context as possible. Over-communicate to give the most details to the reader.
+- Include the steps to reproduce the issue or the reason for adding the feature.
+- Screenshots, videos etc., are highly appreciated.
+
+### Pull Requests
+
+#### Pull Request Process
+
+We follow the ["fork-and-pull" Git workflow](https://github.com/susam/gitpr)
+
+1. Fork the repo
+2. Clone the project
+3. Create a new branch with a descriptive name
+4. Commit your changes to the new branch
+5. Add [changeset](#changeset) if applicable
+6. Push changes to your fork
+7. Open a PR in our repository and tag one of the maintainers to review your PR
+
+Here are some tips for a high-quality pull request:
+
+- Create a title for the PR that accurately defines the work done.
+- Structure the description neatly to make it easy to consume by the readers. For example, you can include bullet points and screenshots instead of having one large paragraph.
+- Add the link to the issue if applicable.
+- Have a good commit message that summarises the work done.
+
+Once you submit your PR:
+
+- We may ask questions, request additional information or ask for changes to be made before a PR can be merged. Please note that these are to make the PR clear for everyone involved and aims to create a frictionless interaction process.
+- As you update your PR and apply changes, mark each conversation resolved.
+
+Once the PR is approved, we'll "squash-and-merge" to keep the git commit history clean.
+
+### Changeset
+
+When adding new features or fixing bugs, we'll need to bump the package versions. We use [Changesets](https://github.com/changesets/changesets) to do this.
+
+> Note: Only changes to the codebase that affect the public API or existing behavior (e.g. bugs) need changesets.
+
+Each changeset defines the version should be a major/minor/patch release, as well as providing release notes that will be added to the changelog upon release.
+
+To create a new changeset, run `yarn changeset add`. This will run the Changesets CLI, prompting you for details about the change. You’ll be able to edit the file after it’s created — don’t worry about getting everything perfect up front.
+
+Since we’re currently in beta, all changes should be marked as a minor/patch release to keep us within the `v0.x` range.
+
+Even though you can technically use any markdown formatting you like, headings should be avoided since each changeset will ultimately be nested within a bullet list. Instead, bold text should be used as section headings.
+
+If your PR is making changes to an area that already has a changeset (e.g. there’s an existing changeset covering theme API changes but you’re making further changes to the same API), you should update the existing changeset in your PR rather than creating a new one.
+
+## Developer Guide
+
+You can find a detailed guide on [`contributors/DEVELOPER-GUIDE.md`](contributors/DEVELOPER-GUIDE.md)