### Install Project Dependencies Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/connector-wagmi/README.md Install the necessary project dependencies using your preferred package manager. These commands fetch all required packages as defined in the `package.json` file, preparing the project for development. ```bash npm install ``` ```bash yarn install ``` -------------------------------- ### Install Example Dependencies with Yarn Source: https://github.com/getpara/examples-hub/blob/main/README.md This command installs all necessary project dependencies for the selected example using Yarn. Ensure Yarn is installed globally or use the appropriate package manager for the specific example if different. ```Bash yarn install ``` -------------------------------- ### Install Dependencies and Start Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-tanstack-start/para-provider/README.md This snippet provides commands to install project dependencies and start the development server for the Para SDK with TanStack Start project. It also includes instructions for setting up the environment variables. ```bash # Install dependencies npm install # Create .env file from example cp .env.example .env # Add your Para API key to the .env file # VITE_PARA_API_KEY=your_api_key # VITE_PARA_ENVIRONMENT=BETA # Start the development server npm run dev ``` ```bash # Install dependencies yarn install # Create .env file from example cp .env.example .env # Add your Para API key to the .env file # VITE_PARA_API_KEY=your_api_key # VITE_PARA_ENVIRONMENT=BETA # Start the development server yarn dev ``` ```bash # Install dependencies bun install # Create .env file from example cp .env.example .env # Add your Para API key to the .env file # VITE_PARA_API_KEY=your_api_key # VITE_PARA_ENVIRONMENT=BETA # Start the development server bun dev ``` -------------------------------- ### Run Local Development Server with npm or Yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-ethers-v5/README.md Start the development server to run the Para SDK example locally. This command compiles and serves the application, making it accessible in your browser for testing the Para SDK integration and signing functionalities. ```Bash npm run dev ``` ```Bash yarn dev ``` -------------------------------- ### Install Project Dependencies with npm or Yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-ethers-v5/README.md Install all necessary project dependencies using your preferred package manager (npm or Yarn). This command fetches and sets up the required libraries and modules for the Para SDK example to function correctly. ```Bash npm install ``` ```Bash yarn install ``` -------------------------------- ### Install Project Dependencies Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-viem-v2/README.md Installs the necessary project dependencies using either npm or yarn package managers, preparing the environment for running the example. ```bash npm install # or yarn install ``` -------------------------------- ### Start Para Example Development Server with npm/yarn/pnpm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal-cosmos/README.md Execute this command to start the Vite development server. This will make the example application accessible locally, typically at `http://localhost:5173`, allowing interaction with the Para Modal and Cosmos Wallet integration. ```bash npm run dev # or yarn dev # or pnpm dev ``` -------------------------------- ### Start Next.js Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/connector-wagmi/README.md Initiate the Next.js development server using your preferred package manager. This command compiles the project and makes it accessible via a local URL, typically `http://localhost:3000`, for testing and development. ```bash npm run dev ``` ```bash yarn dev ``` -------------------------------- ### Start Next.js Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/connector-rainbowkit/README.md This snippet shows how to start the Next.js development server. Execute `npm run dev` or `yarn dev` to launch the application. Once started, open your browser to `http://localhost:3000` to view the running example. ```bash npm run dev # or yarn dev ``` -------------------------------- ### Start Development Server with npm or yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal-cosmos/README.md These commands initiate the development server, making the example application accessible in your browser. Choose the command corresponding to your package manager to start the application. ```bash npm run dev ``` ```bash yarn dev ``` -------------------------------- ### Install Para Example Project Dependencies with npm/yarn/pnpm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal-cosmos/README.md Use your preferred package manager (npm, yarn, or pnpm) to install all necessary project dependencies. This step prepares the environment for running the Para Modal + Cosmos Wallets example. ```bash npm install # or yarn install # or pnpm install ``` -------------------------------- ### Run Development Server for Para Example Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-viem-v1/README.md Start the local development server to run the Para signing example in your browser. The application will typically be available at http://localhost:3000. ```Bash npm run dev ``` ```Bash yarn dev ``` -------------------------------- ### Run Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-viem-v2/README.md Starts the local development server, making the Para SDK example accessible in your web browser for testing and interaction. ```bash npm run dev # or yarn dev ``` -------------------------------- ### Start Vite Development Server for Para Example Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal-multichain/README.md After installing dependencies, launch the development server using Vite. This will compile and serve the application locally, typically on http://localhost:5173. Open this address in your browser to interact with the Para Modal and test the multichain wallet integration. ```bash npm run dev # or yarn dev # or pnpm dev ``` -------------------------------- ### Install Para Example Project Dependencies Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal-evm/README.md Install the necessary project dependencies using npm, yarn, or pnpm to set up the development environment for the Para Modal example. This step ensures all required packages are available. ```bash npm install # or yarn install # or pnpm install ``` -------------------------------- ### Start Development Server with npm or yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-solana-anchor/README.md Execute this command to start the local development server. Once running, you can access the example application in your web browser at the specified port, typically localhost:3000. ```Bash npm run dev ``` ```Bash yarn dev ``` -------------------------------- ### Start Vite Development Server to Run Para RainbowKit Example Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/connector-rainbowkit/README.md Initiate the Vite development server to run the example application. Once started, open the provided local address in your browser to interact with the Para RainbowKit connector. This allows for local testing and development. ```bash npm run dev # or yarn dev # or pnpm dev ``` -------------------------------- ### Start React Development Server with npm/yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-provider/README.md This snippet shows how to initiate the development server for your application. After executing the command using npm or yarn, the server will start, typically on http://localhost:3000. Open this URL in your web browser to view the running example. ```bash npm run dev # or yarn dev ``` -------------------------------- ### Install Project Dependencies with npm or yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-viem-v1/README.md Install required packages for the Para SDK and Viem v1 example. Use either npm or yarn based on your preference. ```Bash npm install ``` ```Bash yarn install ``` -------------------------------- ### Start Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-solana-web3/README.md Launches the local development server to run the Para SDK example application. The application will be accessible via a web browser at the specified port. ```Shell npm run dev # or yarn dev ``` -------------------------------- ### Start Development Server for Para Modal Example Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal-evm/README.md Launch the development server to run the Para Modal example application. This will typically open the application in your browser at `http://localhost:3000` for testing and development. ```bash npm run dev # or yarn dev ``` -------------------------------- ### Run Development Server for Para PWA Example Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-pwa/README.md Execute these commands to start the local development server. This will make the PWA example accessible in your browser, typically at `http://localhost:3000`. This step is required to test the Para integration locally. ```bash npm run dev ``` ```bash yarn dev ``` -------------------------------- ### Install Node.js Project Dependencies Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal-multichain/README.md Installs all required packages for the Para Modal example using either npm or yarn. This step ensures all necessary libraries are available before running the application. ```bash npm install # or yarn install ``` -------------------------------- ### Run Capsule Electron Demo Application Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-electronjs/README.md This snippet provides the necessary commands to clone the Capsule Electron example repository, install its dependencies, and launch the application. It's a quick way to test a working integration. ```bash git clone https://github.com/your-username/capsule-electron-example.git cd capsule-electron-example npm install npm start ``` -------------------------------- ### Run Para Ethers Example Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-ethers-v6/README.md Start the local development server to run the Para Ethers example application. This command compiles the project and makes it accessible via a web browser, typically at localhost:3000. ```Bash npm run dev # or yarn dev ``` -------------------------------- ### Install Project Dependencies for Para PWA Example Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-pwa/README.md Use these commands to install the necessary project dependencies. Choose either `npm` or `yarn` based on your preferred package manager. This step ensures all required libraries, including the Para React SDK, are available for the application. ```bash npm install ``` ```bash yarn install ``` -------------------------------- ### Install Project Dependencies with npm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-pregen-claim/README.md This command installs all required project dependencies using npm. Ensure you have Node.js and npm installed on your system before running this command. It prepares the project for development or production use by downloading necessary packages. ```bash npm install ``` -------------------------------- ### Start Development Server with npm or Yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal/README.md Starts the local development server for the Para Modal example application. This command compiles the project and makes it accessible via a web browser, typically at http://localhost:3000. ```bash npm run dev ``` ```bash yarn dev ``` -------------------------------- ### Install Node.js Project Dependencies with npm, yarn, or pnpm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/custom-oauth-auth/README.md This snippet provides commands to install all required project dependencies. Users can choose between npm, yarn, or pnpm to set up the development environment. Successful installation is a prerequisite for running the example application. ```bash npm install # or yarn install # or pnpm install ``` -------------------------------- ### Install Project Dependencies with npm, yarn, or pnpm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal-multichain/README.md Before running the example, install all required project dependencies. Use your preferred package manager (npm, yarn, or pnpm) to download and set up the necessary libraries. This step ensures all components, including the Para React SDK, are available. ```bash npm install # or yarn install # or pnpm install ``` -------------------------------- ### Start Vite Development Server for Para Example Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal-solana/README.md Initiates the Vite development server, making the Para Modal + Solana Wallets example accessible locally via a web browser, typically at http://localhost:5173. This allows for interaction with the integrated features. ```bash npm run dev # or yarn dev # or pnpm dev ``` -------------------------------- ### Install Project Dependencies with npm, yarn, or pnpm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/signer-ethers/README.md Use one of these commands to install all required project dependencies. This step prepares your development environment by fetching necessary libraries and packages for the Para SDK example. ```bash npm install # or yarn install # or pnpm install ``` -------------------------------- ### Install Project Dependencies with npm or yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/connector-rainbowkit/README.md This snippet demonstrates how to install the required project dependencies. Use either `npm install` or `yarn install` based on your preferred package manager. This step is crucial before running the development server. ```bash npm install # or yarn install ``` -------------------------------- ### Start Vite Development Server for Para Ethers Example Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/signer-ethers/README.md Execute this command to launch the Vite development server. Once running, open the provided local address in your browser to interact with the Para SDK and Ethers.js signing example. ```bash npm run dev # or yarn dev # or pnpm dev ``` -------------------------------- ### Install Project Dependencies with Yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-pregen-claim/README.md This command installs all required project dependencies using Yarn. Ensure you have Node.js and Yarn installed on your system before running this command. It prepares the project for development or production use by downloading necessary packages. ```bash yarn install ``` -------------------------------- ### Install Para Ethers Example Dependencies Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-ethers-v6/README.md Use npm or yarn to install all necessary project dependencies. This step ensures that all required packages, including the Para SDK and Ethers.js, are available for the application to run correctly. ```Bash npm install # or yarn install ``` -------------------------------- ### Start Vite Development Server for Para Auth Example Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/custom-phone-auth/README.md This snippet provides commands to start the Vite development server, making the Para custom phone authentication example accessible locally. After running, open the specified URL in your browser to interact with the application. ```bash npm run dev # or yarn dev # or pnpm dev ``` -------------------------------- ### Run Para Modal Example Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal-evm/README.md Start the Vite development server to run the Para Modal example locally. This will open a local address in your browser, allowing you to interact with the RainbowKit connector and test the integration. ```bash npm run dev # or yarn dev # or pnpm dev ``` -------------------------------- ### Start Local Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal-multichain/README.md Launches the development server for the Para Modal example. This makes the application accessible via a web browser, typically at http://localhost:3000, for testing and interaction. ```bash npm run dev # or yarn dev ``` -------------------------------- ### Run Vite Development Server for Para Example Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-provider/README.md This snippet demonstrates how to start the Vite development server, which hosts the Para integration example locally. Once running, you can access the application in your browser to interact with the ParaModal and RainbowKit connector. ```bash npm run dev # or yarn dev # or pnpm dev ``` -------------------------------- ### Start Next.js Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/custom-oauth-auth/README.md Commands to start the Next.js development server. After execution, the example application will be accessible via a web browser at the specified port, typically http://localhost:3000. ```bash npm run dev # or yarn dev ``` -------------------------------- ### Install Project Dependencies with npm or yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal-evm/README.md Install the necessary project dependencies using either npm or yarn. This step ensures all required packages for the Para Modal example, including the Para React SDK, are available. ```bash npm install # or yarn install ``` -------------------------------- ### Start Vite Development Server for Para Modal Example Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal/README.md This snippet shows how to launch the Vite development server, making the Para Modal example accessible in your browser. It allows you to interact with the application and observe the integration of the Para React SDK. ```bash npm run dev ``` ```bash yarn dev ``` ```bash pnpm dev ``` -------------------------------- ### Install Flutter Project Dependencies Source: https://github.com/getpara/examples-hub/blob/main/mobile/with-flutter/README.md Execute this command in your project's root directory to download and install all necessary Flutter packages and dependencies. This step ensures that the Para SDK and other project libraries are correctly resolved and available for compilation. ```Bash flutter pub get ``` -------------------------------- ### Install Project Dependencies Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-solana-web3/README.md Installs all necessary project dependencies using either npm or yarn package managers. This step ensures all required libraries, including the Para SDK, are available. ```Shell npm install # or yarn install ``` -------------------------------- ### Install Project Dependencies for Para Wagmi Example Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/connector-wagmi/README.md Before running the application, install all required project dependencies. Use npm, yarn, or pnpm to fetch the necessary packages. This step ensures the development environment is correctly set up with all components, including Wagmi and Para connectors. ```bash npm install # or yarn install # or pnpm install ``` -------------------------------- ### Start Next.js Development Server (Yarn/npm) Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-bulk-pregen/README.md Starts the Next.js development server, making the application accessible locally. This allows developers to view and test the application in a browser, typically at http://localhost:3000. ```bash yarn dev ``` ```bash npm run dev ``` -------------------------------- ### Install Project Dependencies with npm, Yarn, or pnpm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal/README.md This snippet provides commands to install all necessary project dependencies using common package managers. Running one of these commands is a crucial first step to set up the development environment for the Para Modal example. ```bash npm install ``` ```bash yarn install ``` ```bash pnpm install ``` -------------------------------- ### Run Para Wagmi Example with Vite Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/connector-wagmi/README.md Start the Vite development server to launch the Para Wagmi example application locally. This command will typically open the application in your browser at http://localhost:5173. Interacting with the RainbowKit connector will demonstrate the Para integration. ```bash npm run dev # or yarn dev # or pnpm dev ``` -------------------------------- ### Start Next.js Development Server with npm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-pregen-claim/README.md This command starts the Next.js development server using npm. After execution, the application will typically be accessible at `http://localhost:3000` in your web browser. This server provides live reloading and error reporting for efficient development. ```bash npm run dev ``` -------------------------------- ### Install Project Dependencies with npm or yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal-cosmos/README.md These commands demonstrate how to install the necessary project dependencies using either npm or yarn. Run one of these commands in your terminal to prepare the project for development. ```bash npm install ``` ```bash yarn install ``` -------------------------------- ### Configure Environment Variables for an Example Source: https://github.com/getpara/examples-hub/blob/main/README.md Copy the example environment file to a new `.env` file and then edit it to provide necessary API keys, RPC URLs, or other configuration settings required by the application. ```Bash # Example using .env cp .env.example .env # Now edit .env with your values using your preferred editor nano .env ``` -------------------------------- ### Install Project Dependencies with npm or Yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/client-auth-server-sign/README.md Installs all required project dependencies using either npm or Yarn package managers to prepare the application for development or deployment. ```bash npm install ``` ```bash yarn install ``` -------------------------------- ### Install Project Dependencies for Svelte Vite App Source: https://github.com/getpara/examples-hub/blob/main/web/with-svelte-vite/para-modal/README.md Install all necessary project dependencies using npm or yarn. This step ensures all required packages for the Svelte application are available before development or running the example. ```bash npm install # or yarn install ``` -------------------------------- ### Install Dependencies for Para Expo Project Source: https://github.com/getpara/examples-hub/blob/main/mobile/with-expo/README.md These commands install all required Node.js packages for the Para Expo example application. You can use either npm or yarn as your package manager. This step must be completed before attempting to run the application. ```bash npm install ``` ```bash yarn install ``` -------------------------------- ### Install Project Dependencies (Yarn/npm) Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-bulk-pregen/README.md Installs all required project dependencies using either Yarn or npm. This step ensures all necessary packages are available for the Next.js application to run correctly. ```bash yarn install ``` ```bash npm install ``` -------------------------------- ### Install Project Dependencies with npm, pnpm, yarn, or bun Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-relay-bridge-api/README.md Install all necessary project dependencies using your preferred package manager. This step ensures that all required libraries and modules for the Para Relay Bridge example are available before running the application. ```bash npm install # or pnpm install # or yarn install # or bun install ``` -------------------------------- ### Start Vite Development Server for Para Chrome Extension Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-chrome-extension/README.md This snippet shows how to start the Vite development server to run the Para Chrome Extension example. This command compiles the project and serves it locally, allowing interaction with the Para Modal. ```bash npm run dev # or yarn dev # or pnpm dev ``` -------------------------------- ### Install iOS Dependencies for React Native Source: https://github.com/getpara/examples-hub/blob/main/mobile/with-react-native/README.md This sequence of commands installs necessary iOS-specific dependencies, including CocoaPods. Navigate into the ios directory, install Ruby gems, and then install pods to ensure proper native module linking. ```Bash cd ios bundle install bundle exec pod install cd .. ``` -------------------------------- ### Install Project Dependencies with npm or yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal-solana/README.md This snippet provides commands to install the necessary project dependencies. Use either `npm install` or `yarn install` based on your preferred package manager. These dependencies are required for the example to run correctly. ```bash npm install # or yarn install ``` -------------------------------- ### Start Development Server (npm/Yarn) Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-cosmjs/README.md Launch the development server using your preferred package manager. These commands typically start a local server, allowing you to view and interact with the application in your browser at http://localhost:3000. ```bash npm run dev ``` ```bash yarn dev ``` -------------------------------- ### Navigate to Node.js Server Example Directory Source: https://github.com/getpara/examples-hub/blob/main/server/with-node/README.md Change your current working directory to the Node.js server example project. This step is crucial for executing subsequent installation and run commands within the correct context. Adjust the path if your project structure differs. ```Bash cd examples-hub/server/with-node # Adjust path if necessary ``` -------------------------------- ### Run Development Server for Para Modal Example Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal-solana/README.md This snippet shows how to start the local development server. Execute either `npm run dev` or `yarn dev` to launch the application. Once running, you can access the example in your browser at `http://localhost:3000`. ```bash npm run dev # or yarn dev ``` -------------------------------- ### Install Project Dependencies with npm or yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-solana-anchor/README.md Use this command to install all necessary project dependencies. Choose either npm or yarn based on your preferred package manager to set up the development environment. ```Bash npm install ``` ```Bash yarn install ``` -------------------------------- ### Configure Para API Key for Next.js Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/connector-wagmi/README.md Before running the Para Wagmi example, obtain your Para API key from the developer portal. Create a `.env.local` file and add your key, ensuring it's prefixed with `NEXT_PUBLIC_` for browser exposure. ```env NEXT_PUBLIC_PARA_API_KEY=your_api_key_here ``` -------------------------------- ### Install Project Dependencies Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/custom-phone-auth/README.md These commands install all required project dependencies using either npm or yarn. Run one of these in your project's root directory after cloning the repository. ```bash npm install ``` ```bash yarn install ``` -------------------------------- ### Start Next.js Development Server with Yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-pregen-claim/README.md This command starts the Next.js development server using Yarn. After execution, the application will typically be accessible at `http://localhost:3000` in your web browser. This server provides live reloading and error reporting for efficient development. ```bash yarn dev ``` -------------------------------- ### Install Node.js Project Dependencies Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-provider/README.md This snippet provides commands to install all necessary project dependencies. It supports common Node.js package managers like npm, yarn, and pnpm, ensuring the project is ready for development. ```bash npm install # or yarn install # or pnpm install ``` -------------------------------- ### Start Next.js Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/custom-phone-auth/README.md These commands start the Next.js development server using either npm or yarn. Once running, open your browser to http://localhost:3000 to view the application. ```bash npm run dev ``` ```bash yarn dev ``` -------------------------------- ### Install Project Dependencies (npm, yarn, pnpm) Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/connector-rainbowkit/README.md Install all required project dependencies using your preferred package manager. This step ensures all necessary libraries and modules are available for the application to run correctly. ```bash npm install # or yarn install # or pnpm install ``` -------------------------------- ### Create Local Environment File (Bash) Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-bulk-pregen/README.md Copies the example environment file (.env.example) to a local one (.env.local). This file will store sensitive information like API keys for local development. ```bash cp .env.example .env.local ``` -------------------------------- ### Start Vite Development Server for Local Application Access Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/custom-oauth-auth/README.md This snippet outlines how to start the Vite development server, making the example application accessible locally. Use your preferred package manager (npm, yarn, or pnpm) to execute the command. The server typically runs on `http://localhost:5173`, allowing interaction with the RainbowKit connector. ```bash npm run dev # or yarn dev # or pnpm dev ``` -------------------------------- ### Install Project Dependencies with npm, yarn, or pnpm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal-solana/README.md Installs all necessary project dependencies using the preferred package manager: npm, yarn, or pnpm. This step is crucial before running the application to ensure all required libraries are available. ```bash npm install # or yarn install # or pnpm install ``` -------------------------------- ### Start Node.js Development Server Source: https://github.com/getpara/examples-hub/blob/main/server/with-node/README.md Initiate the Node.js development server, which will host the Para integration examples. Upon successful startup, the server will typically be accessible for requests at http://localhost:3000. This command enables testing of the API endpoints. ```Bash yarn dev ``` ```Bash npm run dev ``` -------------------------------- ### Run the Development Application Server Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-squid-router-api/README.md Start the development server to run the application locally. This command launches the web server, making the application accessible in your browser for testing and development purposes. ```bash npm run dev # or pnpm dev # or yarn dev # or bun dev ``` -------------------------------- ### Start Next.js Development Server (npm/Yarn) Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/custom-email-auth/README.md Launch the Next.js development server to run the application locally. After execution, the example will be accessible in your web browser, typically at http://localhost:3000. ```bash npm run dev ``` ```bash yarn dev ``` -------------------------------- ### Install Project Dependencies (npm/Yarn) Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/custom-email-auth/README.md Install all necessary project dependencies before running the application. Choose your preferred package manager, npm or Yarn, to download the required packages. ```bash npm install ``` ```bash yarn install ``` -------------------------------- ### Install Node.js Project Dependencies Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-squid-router-api/README.md Install all necessary project dependencies using your preferred Node.js package manager. This step ensures that all required libraries and modules are available, preparing the application for development or deployment. ```bash npm install # or pnpm install # or yarn install # or bun install ``` -------------------------------- ### Clone the Para Examples Hub Repository Source: https://github.com/getpara/examples-hub/blob/main/README.md This command clones the entire `examples-hub` repository from GitHub to your local machine and then changes the current directory into the cloned repository. ```Bash git clone https://github.com/getpara/examples-hub.git cd examples-hub ``` -------------------------------- ### Install Project Dependencies (npm/Yarn) Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-cosmjs/README.md Install the necessary project dependencies using your preferred package manager. These commands fetch all required packages defined in your package.json file, ensuring the project runs correctly. ```bash npm install ``` ```bash yarn install ``` -------------------------------- ### Start Svelte Vite Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-svelte-vite/para-modal/README.md Launch the development server for the Svelte application using Vite. This command compiles the project and serves it locally, allowing you to view and test the application in your browser, typically at http://localhost:5173. ```bash npm run dev # or yarn dev ``` -------------------------------- ### Start React Native Metro Bundler Source: https://github.com/getpara/examples-hub/blob/main/mobile/with-react-native/README.md This command starts the Metro bundler, which compiles and serves your JavaScript code to the React Native application. It must run in a separate terminal while developing. ```Bash npx react-native start ``` -------------------------------- ### Install Para SDK Dependencies with npm/yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-provider/README.md This snippet outlines the process for installing the required dependencies for the Para SDK. You can use either npm or yarn, popular package managers, to add all necessary packages to your project. This step is crucial before running the application. ```bash npm install # or yarn install ``` -------------------------------- ### Clone Para Bulk Pregen Wallet Repository (Bash) Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-bulk-pregen/README.md Clones the Para bulk pre-generation wallet example repository from Git and navigates into its directory. This is the initial step to set up the project locally. ```bash git clone cd ``` -------------------------------- ### Install Node.js Dependencies for React Native Source: https://github.com/getpara/examples-hub/blob/main/mobile/with-react-native/README.md This command installs all required Node.js packages for the React Native project. Use either npm or yarn based on your preference to fetch project dependencies. ```Bash npm install # or yarn install ``` -------------------------------- ### Configure Para API Key in .env.local Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-viem-v1/README.md Set up your Para API key in a .env.local file for secure access to the Para Developer Portal. Replace 'your_para_api_key_here' with your actual key. ```Env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Install Project Dependencies with npm or Yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-vue-vite/para-modal/README.md Install all required project dependencies using either npm or Yarn. This step prepares the development environment by downloading necessary packages defined in the project's package.json file. ```bash npm install ``` ```bash yarn install ``` -------------------------------- ### Install Capsule Electron Project Dependencies Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-electronjs/README.md This command installs all required npm packages for integrating Capsule into an Electron project. It includes the Capsule React SDK, various polyfills for Node.js core modules, and Babel/Webpack loaders for React support. ```bash npm install @usecapsule/react-sdk buffer crypto-browserify process react react-dom stream-browserify vm-browserify @babel/core @babel/preset-env @babel/preset-react babel-loader css-loader style-loader --save ``` -------------------------------- ### Navigate to a Specific Example Directory Source: https://github.com/getpara/examples-hub/blob/main/README.md Use this command to change your current working directory to a specific example within the repository, such as the `para-modal` example for React and Next.js. ```Bash # Example: Navigate to the Para Modal example using React + Next.js cd web/with-react-nextjs/para-modal ``` -------------------------------- ### Install Project Dependencies with npm or Yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/custom-oauth-auth/README.md Instructions for installing project dependencies using either npm or Yarn package managers. This step is required before running the development server. ```bash npm install # or yarn install ``` -------------------------------- ### Install Node.js Dependencies with npm or Yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal/README.md Installs all required project dependencies using either npm or Yarn. This step ensures that all necessary packages, including the Para React SDK, are available for the application to run. ```bash npm install ``` ```bash yarn install ``` -------------------------------- ### Install Project Dependencies with npm, yarn, or pnpm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/custom-phone-auth/README.md This snippet shows how to install the project's required dependencies using common Node.js package managers: npm, yarn, or pnpm. This step prepares the project environment for development. ```bash npm install # or yarn install # or pnpm install ``` -------------------------------- ### Start Next.js Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/client-auth-server-sign/README.md Launches the Next.js development server, making the application accessible locally for testing and development purposes, typically at http://localhost:3000. ```bash npm run dev ``` ```bash yarn dev ``` -------------------------------- ### Install Bun Dependencies for Para SDK Project Source: https://github.com/getpara/examples-hub/blob/main/server/with-bun/README.md This snippet shows how to install the necessary project dependencies using Bun's package manager. Ensure Bun is installed and configured on your system before running this command. This step is crucial for setting up the development environment. ```bash bun install ``` -------------------------------- ### Configure Para API Key Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-viem-v2/README.md Sets up the Para API key in a local environment file (`.env.local`) for application access, which is a prerequisite for using the Para SDK. ```env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Install Project Dependencies for Vue Vite Source: https://github.com/getpara/examples-hub/blob/main/web/with-vue-vite/connector-wagmi/README.md This snippet provides commands to install the necessary project dependencies using either npm or yarn. This step is crucial and must be completed before attempting to run the application. ```bash npm install # or yarn install ``` -------------------------------- ### Configure Para API Key in .env.local Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-ethers-v5/README.md Set your Para API key in the project's `.env.local` file. This key is crucial for authenticating with the Para Developer Portal and enabling the full functionality of the Para SDK within the example application. ```env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Run the Para Relay Bridge Application Locally Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-relay-bridge-api/README.md Start the development server to run the Para Relay Bridge application locally. Once started, the application will be accessible via your web browser, allowing you to interact with the Para authentication and Relay bridging functionalities. ```bash npm run dev # or pnpm dev # or yarn dev # or bun dev ``` -------------------------------- ### Install Project Dependencies with Yarn Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-jupiter-dex-api/README.md This command installs all necessary project dependencies using Yarn. Ensure Yarn is installed on your system before running this command to set up the project environment. ```bash yarn install ``` -------------------------------- ### Install Project Dependencies with npm, yarn, or pnpm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/custom-email-auth/README.md This snippet provides commands to install the project's required dependencies. Choose your preferred package manager (npm, yarn, or pnpm) to set up the development environment. ```bash npm install ``` ```bash yarn install ``` ```bash pnpm install ``` -------------------------------- ### Start Next.js Development Server Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-jupiter-dex-api/README.md This command starts the Next.js development server, making the application accessible locally. The app will typically run on http://localhost:3000, allowing for local development and testing. ```bash yarn dev ``` -------------------------------- ### cURL Example: Create Para Pre-Generated Wallet Source: https://github.com/getpara/examples-hub/blob/main/server/with-bun/README.md This cURL command demonstrates how to make a POST request to the `/wallets/create` endpoint. Replace 'user@example.com' with the desired email and ensure the server is running on 'http://localhost:8000'. This example shows the required content type and request body. ```bash curl -X POST http://localhost:8000/wallets/create -H "Content-Type: application/json" -d '{"email": "user@example.com"}' ``` -------------------------------- ### Start Vue Vite Development Server Source: https://github.com/getpara/examples-hub/blob/main/web/with-vue-vite/connector-wagmi/README.md This snippet shows the commands to start the Vite development server for the Vue.js application. After execution, the application will be accessible via a local URL in your browser, typically http://localhost:5173. ```bash npm run dev # or yarn dev ``` -------------------------------- ### Start Vite Development Server with npm, yarn, or pnpm Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/custom-email-auth/README.md This snippet shows how to start the Vite development server. Running this command will launch the application locally, typically accessible via `http://localhost:5173`, allowing interaction with the RainbowKit connector. ```bash npm run dev ``` ```bash yarn dev ``` ```bash pnpm dev ``` -------------------------------- ### Run Para Flutter Example on Device Source: https://github.com/getpara/examples-hub/blob/main/mobile/with-flutter/README.md To launch the application, first ensure an emulator is running or a physical device is connected and recognized by Flutter. Use this command, replacing with the target device's identifier, to run the Para Flutter example application. ```Bash flutter run -d ``` -------------------------------- ### Configure Para API Key in .env.local Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-pwa/README.md This snippet shows how to set up your Para API key in a `.env.local` file for local development. Replace `your_para_api_key_here` with your actual key obtained from the Para Developer Portal. This key is crucial for authenticating your application with Para services. ```env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Start Deno Para SDK Server with Task Runner Source: https://github.com/getpara/examples-hub/blob/main/server/with-deno/README.md This command starts the Deno server using a defined task, typically configured in `deno.json` or `deno.jsonc`. It's the recommended way to run the server for development, leveraging Deno's task runner for consistent execution. ```Bash deno task dev ``` -------------------------------- ### Start Vite Development Server with npm or Yarn Source: https://github.com/getpara/examples-hub/blob/main/web/with-vue-vite/para-modal/README.md Launch the Vite development server to run the Vue application locally. This command compiles and serves the application, enabling live development with hot module replacement. ```bash npm run dev ``` ```bash yarn dev ``` -------------------------------- ### Configure Para API Key in .env.local Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal-cosmos/README.md This snippet shows how to set up your Para API key in a `.env.local` file, which is essential for authenticating with the Para API. Replace 'your_para_api_key_here' with your actual key obtained from the Para Developer Portal. ```env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Install Project Dependencies for Para Chrome Extension Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-chrome-extension/README.md This snippet demonstrates how to install the necessary project dependencies using common package managers. Choose your preferred manager (npm, yarn, or pnpm) to set up the development environment. ```bash npm install # or yarn install # or pnpm install ``` -------------------------------- ### Configure Environment Variables for Next.js Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-jupiter-dex-api/README.md This snippet shows how to copy the example environment file and configure essential API keys and RPC URLs for the Next.js application. It requires a Para API key from developer.getpara.com and a Solana mainnet RPC URL. ```bash cp .env.example .env.local NEXT_PUBLIC_PARA_API_KEY=your-para-api-key NEXT_PUBLIC_MAINNET_RPC_URL=your-mainnet-rpc-url ``` -------------------------------- ### Configure Para API Key in .env.local Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-solana-web3/README.md Sets up the Para API key in a local environment file for secure access to Para services. This key is essential for authentication and interacting with the Para SDK. ```Shell NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Install Node.js Project Dependencies Source: https://github.com/getpara/examples-hub/blob/main/server/with-node/README.md Execute this command to download and install all necessary Node.js packages defined in the project's package.json. This ensures all required libraries, including the Para SDK, are available for the application to run. Use either yarn install or npm install based on your preferred package manager. ```Bash yarn install ``` ```Bash npm install ``` -------------------------------- ### React Component Props API Reference Example Source: https://github.com/getpara/examples-hub/blob/main/server/with-node/public/index.html This section provides a conceptual API documentation for a React component's props, demonstrating how to define and describe the expected inputs. It outlines the property names, their types, and a brief explanation of their purpose, crucial for component reusability and maintainability. ```APIDOC interface UserProfileProps { /** * The unique identifier for the user. * @type {string} * @required */ userId: string; /** * The full name of the user. * @type {string} * @required */ fullName: string; /** * The user's email address. * @type {string} * @optional */ email?: string; /** * The URL to the user's profile picture. * @type {string} * @optional */ avatarUrl?: string; /** * Callback function invoked when the user profile is clicked. * @param {string} userId - The ID of the clicked user. * @returns {void} * @optional */ onClick?: (userId: string) => void; } ``` -------------------------------- ### Initialize Capsule Client in JavaScript Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-electronjs/README.md This snippet demonstrates how to create a new Capsule client instance. It requires importing `Capsule` and `Environment` from the `@usecapsule/react-sdk` and providing an `Environment` (e.g., BETA) along with your API key to the constructor. ```javascript import Capsule, { Environment } from "@usecapsule/react-sdk"; const capsule = new Capsule(Environment.BETA, "YOUR_API_KEY"); ``` -------------------------------- ### Install Deno Dependencies for Para SDK Server Source: https://github.com/getpara/examples-hub/blob/main/server/with-deno/README.md This command uses `deno cache --reload` to ensure all dependencies for the Deno server are downloaded and cached. It's an optional step for initial setup or when dependencies change, ensuring a clean dependency state. ```Bash deno cache --reload server.ts ``` -------------------------------- ### Configure Para API Key for Wagmi Integration Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/connector-wagmi/README.md To enable the Para Wagmi Wallet Connector, obtain your Para API key from the developer portal. Add this key to a .env file in your project root, ensuring it's prefixed with VITE_ for client-side access. This setup is crucial for the connector's functionality. ```env VITE_PARA_API_KEY=your_api_key_here ``` -------------------------------- ### Configure Environment Variables for Para and Squid Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-squid-router-api/README.md Create a '.env' file based on 'env.example' to configure essential API keys, environment settings, integrator ID, and optional RPC URLs for Para and Squid Router. This setup is crucial for connecting to the respective services and blockchain networks, ensuring proper application functionality. ```env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here NEXT_PUBLIC_PARA_ENVIRONMENT=beta NEXT_PUBLIC_SQUID_INTEGRATOR_ID=your_squid_integrator_id NEXT_PUBLIC_ETHEREUM_RPC_URL=https://eth-mainnet.g.alchemy.com/v2/YOUR_KEY NEXT_PUBLIC_BASE_RPC_URL=https://mainnet.base.org NEXT_PUBLIC_SOLANA_RPC_URL=https://api.mainnet-beta.solana.com ``` -------------------------------- ### Configure Webpack for Electron Renderer Process (webpack.renderer.config.js) Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-electronjs/README.md This configuration for `webpack.renderer.config.js` sets up React support by resolving `.js` and `.jsx` extensions. It also includes the same Node.js core module fallbacks and `ProvidePlugin` setup as the main process configuration, ensuring the renderer process can correctly bundle Capsule's dependencies. ```javascript const rules = require("./webpack.rules"); const webpack = require("webpack"); // ... other configurations module.exports = { module: { rules }, resolve: { extensions: [".js", ".jsx"], fallback: { // Same fallback configuration as in webpack.main.config.js } }, plugins: [ // Same plugin configuration as in webpack.main.config.js ] // ... output configuration }; ``` -------------------------------- ### Configure Para API Key in .env.local Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal-evm/README.md Set up your Para API key by creating a `.env.local` file in the project root. This key is essential for authenticating requests with the Para API and enabling the Para Modal functionality. ```env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Configure Para API Key and RPC URLs in .env Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-relay-bridge-api/README.md Set up your environment variables by creating a .env file based on .env.example. This includes your Para API Key, Para Environment, and optional but recommended RPC URLs for Ethereum Sepolia, Base Sepolia, and Solana Devnet. These configurations are crucial for connecting to Para services and blockchain networks. ```env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here NEXT_PUBLIC_PARA_ENVIRONMENT=beta NEXT_PUBLIC_ETHEREUM_SEPOLIA_RPC_URL=https://ethereum-sepolia-rpc.publicnode.com NEXT_PUBLIC_BASE_SEPOLIA_RPC_URL=https://base-sepolia-rpc.publicnode.com NEXT_PUBLIC_SOLANA_DEVNET_RPC_URL=https://api.devnet.solana.com ``` -------------------------------- ### Configure Para API Key in .env for Client-Side Access Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/signer-ethers/README.md This snippet illustrates how to set your Para API key within a `.env` file. Prefixing it with `VITE_` ensures it's exposed to client-side code when using Vite, a common setup for web projects. ```env VITE_PARA_API_KEY=your_api_key_here ``` -------------------------------- ### Configure Para API Key in .env.local Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal/README.md Sets up the Para API key for the application. This key is essential for authenticating requests with the Para API and should be stored securely in a .env.local file in the project root. ```env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Configure Para Swift SDK Environment Variables in Xcode Source: https://github.com/getpara/examples-hub/blob/main/mobile/with-swift/README.md This snippet provides detailed instructions and examples for setting up required and optional environment variables within Xcode's scheme settings. These variables are crucial for configuring the Para Swift SDK, controlling the API key, target environment (e.g., 'beta', 'prod'), custom RPC URLs, and development-specific parameters like relying party ID and JS bridge URL. ```Shell PARA_API_KEY=your_api_key_here # Your Para API key PARA_ENVIRONMENT=beta # Options: "dev", "sandbox", "beta", "prod" PARA_RPC_URL # Custom RPC URL for EVM operations (defaults to Sepolia testnet) PARA_DEV_RELYING_PARTY_ID # Custom relying party ID for dev environment PARA_DEV_JS_BRIDGE_URL # Custom JS bridge URL for dev environment ``` -------------------------------- ### Configure Para API Key in Svelte Vite .env Source: https://github.com/getpara/examples-hub/blob/main/web/with-svelte-vite/para-modal/README.md Set up your Para API key by creating a .env file in the project root. This key is essential for authenticating requests to the Para API. Copy the example file and replace the placeholder with your actual key. ```env VITE_PARA_API_KEY=your_api_key_here ``` -------------------------------- ### Configure Para API Key for Client-Side Access Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal-multichain/README.md To enable the Para SDK, obtain your API key from the Para Developer Portal. Create a .env file in the project root and add your key, ensuring it's prefixed with VITE_ for client-side exposure. This key is essential for authenticating requests to the Para API. ```env VITE_PARA_API_KEY=your_api_key_here ``` -------------------------------- ### Start Bun Development Server with Para SDK Source: https://github.com/getpara/examples-hub/blob/main/server/with-bun/README.md This snippet demonstrates how to start the Bun server in development mode. This mode typically includes features like hot-reloading for a smoother development experience. The server will listen on port 8000 by default. ```bash bun dev ``` -------------------------------- ### Configure Para API Key in .env.local Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-solana-anchor/README.md This snippet shows how to set up your Para API key in a .env.local file. The key is essential for authenticating with the Para API and enabling SDK functionalities. ```Env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Configure Para API Key for Client-Side Access Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/para-modal-solana/README.md Sets up the Para API key by adding it to a .env file, ensuring it's prefixed with VITE_ for client-side exposure in a Vite project. This key is essential for authenticating with the Para API. ```bash VITE_PARA_API_KEY=your_api_key_here ``` -------------------------------- ### Create a Simple React TypeScript Component Source: https://github.com/getpara/examples-hub/blob/main/server/with-node/public/index.html This example shows a basic functional React component written in TypeScript (TSX). It defines an interface for its props to ensure type safety, demonstrating how to pass and use properties within a component. ```TypeScript import React from 'react'; interface HelloWorldProps { name: string; } const HelloWorld: React.FC = ({ name }) => { return (

Hello, {name}!

This is a simple React component with TypeScript.

); }; export default HelloWorld; ``` -------------------------------- ### Configure Para API Key in .env.local (Environment) Source: https://github.com/getpara/examples-hub/blob/main/specialized/with-bulk-pregen/README.md Adds the Para API Key to the .env.local file. This key is essential for the application to interact with the Para SDK and its services. Replace 'your_para_api_key_here' with your actual key. ```env # .env.local PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Configure Para API Key in Next.js .env.local Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/connector-rainbowkit/README.md This snippet shows how to set up your Para API key in a Next.js project. Create a `.env.local` file and add your key, ensuring it's prefixed with `NEXT_PUBLIC_` for browser exposure. This key is essential for authenticating with the Para API. ```env NEXT_PUBLIC_PARA_API_KEY=your_api_key_here ``` -------------------------------- ### Configure Para API Key in .env.local Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-ethers-v6/README.md This snippet shows how to set up your Para API key in a .env.local file. This key is essential for authenticating with the Para Developer Portal and enabling SDK functionality within your application. ```Env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Configure Para API Key in .env for Vite Client Access Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-vite/custom-oauth-auth/README.md This snippet demonstrates how to configure your Para API Key within a `.env` file. The key must be prefixed with `VITE_` to ensure it's exposed to client-side code, enabling proper initialization of the Para SDK. This setup is crucial for the application to interact with the Para API. ```env VITE_PARA_API_KEY=your_api_key_here ``` -------------------------------- ### Configure Node Polyfills for Client-Side Only Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-tanstack-start/para-provider/README.md This snippet shows how to configure Node.js polyfills specifically for the client-side in `app.config.ts` using TanStack Start's configuration. This prevents server-side evaluation issues and ensures `process.browser` is set correctly. ```ts // app.config.ts export default defineConfig({ // ... other config // This applies to both client and server vite: { plugins: [tsConfigPaths({ projects: ["./tsconfig.json"] })], define: { "process.browser": true, }, }, // This applies to client only routers: { client: { vite: { plugins: [nodePolyfills()], }, }, }, }); ``` -------------------------------- ### Configure Para API Key for React SDK Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/para-modal-multichain/README.md Sets the NEXT_PUBLIC_PARA_API_KEY in a .env.local file. This key is essential for authenticating with the Para API and enabling the Para React SDK functionalities. ```env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ``` -------------------------------- ### Configure Para API Key in .env.local Source: https://github.com/getpara/examples-hub/blob/main/web/with-react-nextjs/signer-cosmjs/README.md Set up your Para API key for authentication. Obtain it from the Para Developer Portal and add it to a .env.local file in your project root. This key is essential for accessing Para services. ```env NEXT_PUBLIC_PARA_API_KEY=your_para_api_key_here ```