create-rise-dapp
v0.1.5
Published
Create RISE blockchain dApps with one command
Maintainers
Readme
create-rise-dapp
Create RISE blockchain dApps with one command.
Quick Start
# Install globally (recommended)
npm install -g create-rise-dapp
create-rise-dapp my-rise-dapp
# Or use npx
npx create-rise-dapp my-rise-dappUsage
Interactive Mode
Run without arguments to use the interactive prompts:
npx create-rise-dappWith Arguments
# Create app with specific template
npx create-rise-dapp my-pump-clone --template pump
# Create app with all templates
npx create-rise-dapp my-rise-suite --template all
# Skip all prompts
npx create-rise-dapp my-app -yAvailable Templates
- chat - Real-time messaging with karma system
- pump - Token launchpad like pump.fun
- frenpet - Virtual pet game with VRF battles
- leverage - Leverage trading app
Options
-t, --template <template>- Template to use (chat, pump, frenpet, all)-y, --yes- Skip prompts and use defaults--no-git- Skip git initialization--no-install- Skip dependency installation--legacy- Use old template approach (not recommended)
What's Included
Each template comes with:
- Smart contracts written in Solidity
- Frontend built with Next.js and TypeScript
- Blockchain integration using wagmi
- Real-time updates via WebSocket
- Production-ready UI components
- Deployment scripts
Development
After creating your app:
cd my-rise-dapp
# Deploy contracts
npm run deploy-and-sync
# Start development server
npm run devHow It Works - Direct Template Approach
create-rise-dapp now uses a direct template approach that creates apps directly from the working directories (frontend/, contracts/, scripts/) rather than maintaining separate template files.
Benefits
- ✅ Templates are always up-to-date with latest features
- ✅ No duplicate files to maintain
- ✅ Instant access to bug fixes and improvements
- ✅ Smaller package size (29MB saved!)
Template Configuration
Templates are configured in src/create-app-direct.js:
- TEMPLATE_MAPPINGS - Defines which files belong to each template
- contractConfig - Contains deployed contract addresses
- BASE_FILES - Common files shared across all templates
For Contributors
To add features or modify templates:
- Make changes in the main
/frontend/or/contracts/directories - Update
TEMPLATE_MAPPINGSif adding template-specific files - See Creating Templates Guide for new templates
- See Adding Features Guide for base features
License
MIT
