
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
share-web-cli
Advanced tools
Easy CLI tool to share local web services using ngrok without DNS/firewall configuration
A simple and powerful CLI tool to easily share your local web services to the internet using ngrok without complex DNS and firewall configuration.
npm install -g share-web-cli
npm install
# Share a service running on port 3000
share-web start 3000
# Share a service on port 8080
share-web start 8080
# Check current tunnel status
share-web status
# Stop all tunnels
share-web stop
# Share with specific protocol
share-web start 3000 --protocol https
# Share TCP service (e.g., database)
share-web start 5432 --protocol tcp
# List common development ports
share-web list
# Show current configuration
share-web config show
# Edit configuration
share-web config edit
start [PORT]Start ngrok tunnel for specified port (default: 3000)
Options:
--protocol: Protocol to use (http, https, tcp)Examples:
share-web start 8080
share-web start 3000 --protocol https
share-web start 22 --protocol tcp
stopStop all active ngrok tunnels
Example:
share-web stop
statusShow current tunnel status and access URLs
Example:
share-web status
listList common development ports and their typical uses
Example:
share-web list
configManage ngrok configuration
Subcommands:
show: Display current configurationedit: Open configuration file in your default editorExamples:
share-web config show
share-web config edit
| Port | Typical Use |
|---|---|
| 3000 | Next.js, React development server |
| 8080 | Generic web application |
| 5000 | Flask, Django development |
| 3001 | Alternative React port |
| 8000 | FastAPI, Pyramid development |
| 4200 | Angular development server |
| 5432 | PostgreSQL database |
| 6379 | Redis cache |
| 27017 | MongoDB database |
Share Web CLI uses ngrok to create secure tunnels to your local development servers. When you start a tunnel:
If you get a "port already in use" error:
# Check what's using the port
lsof -i :3000
# Kill the process if needed
kill -9 <PID>
If you get an ngrok error, make sure ngrok is properly installed:
# Download ngrok manually
wget https://bin.equinox.io/c/bNyj1mQVY4c/ngrok-v3-stable-linux-amd64.tgz
tar -xzf ngrok-v3-stable-linux-amd64.tgz
chmod +x ngrok
For persistent ngrok tunnels, you may need to:
# React app
npm start
# Next.js app
npm run dev
# Flask app
python app.py
share-web start 3000
# Start your webhook receiver
python webhook_server.py # running on port 5000
# Create tunnel for webhook testing
share-web start 5000
# Use the public URL in your webhook provider settings
# Start PostgreSQL locally (usually port 5432)
pg_ctl start
# Share database access
share-web start 5432 --protocol tcp
# Others can connect using the provided TCP URL
git checkout -b feature/amazing-feature)git commit -m 'Add some amazing feature')git push origin feature/amazing-feature)This project is licensed under the ISC License - see the LICENSE file for details.
If you encounter any issues or have questions:
Made with ❤️ by MiniMax Agent
FAQs
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.