Gathering detailed insights and metrics for nodemon-ngrok-webpack-plugin
Gathering detailed insights and metrics for nodemon-ngrok-webpack-plugin
Gathering detailed insights and metrics for nodemon-ngrok-webpack-plugin
Gathering detailed insights and metrics for nodemon-ngrok-webpack-plugin
Webpack plugin to start/reload Nodemon server and use ngrok to create tunnel to localhost
npm install nodemon-ngrok-webpack-plugin
Typescript
Module System
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
6 Stars
42 Commits
1 Watchers
14 Branches
1 Contributors
Updated on Nov 29, 2023
Latest Version
1.0.3
Package Id
nodemon-ngrok-webpack-plugin@1.0.3
Unpacked Size
20.62 kB
Size
6.42 kB
File Count
9
NPM Version
6.12.0
Node Version
12.12.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Inspired by lzhaki's nodemon-webpack-plugin, this plugin uses Nodemon to watch and automatically restart your Webpack output node server when Webpack is run in --watch
mode. It then uses ngrok to create an online tunnel to your development server.
This enables you to access your live local Webpack build from any device for easier debugging. Need to test something on a phone or tablet? No problem! Someone else's machine has a bug that can't be reproduced anywhere else? Easy-peasy!
1npm install -D nodemon-ngrok-webpack plugin
nodemon-ngrok-webpack-plugin
requires Webpack >=4 to work.
In your webpack config:
1const path = require('path'); 2const NodeExternals = require('webpack-node-externals'); 3const NodemonNgrokWebpackPlugin = require('nodemon-ngrok-webpack-plugin'); 4 5module.exports = { 6 mode: 'development', 7 target: 'node', 8 externals: [NodeExternals()], 9 entry: './src/server.js', 10 output: { 11 path: path.resolve('./build'), 12 filename: 'server.js' 13 }, 14 plugins: [ 15 // Where the magic happens 16 new NodemonNgrokWebpackPlugin() 17 ], 18}
Run:
1webpack --watch
1webpack is watching the files… 2 ╔════════════════════════════════════════════════════════╗ 3 ║ ║ 4 ║ ngrok Tunnel Running at: https://b30a5d06.ngrok.io ║ 5 ║ ngrok Client: http://localhost:4040 ║ 6 ║ ║ 7 ╚════════════════════════════════════════════════════════╝ 8Hash: b977a3a88dc37e896883 9Version: webpack 4.20.2 10Time: 901ms 11Built at: 10/11/2018 11:43:44 AM 12 Asset Size Chunks Chunk Names 13server.js 5.42 KiB main [emitted] main 14Entrypoint main = server.js 15[./webpack.config.js] 433 bytes {main} [built] 16[nodemon-ngrok-webpack-plugin] external "nodemon-ngrok-webpack-plugin" 42 bytes {main} [built] 17[path] external "path" 42 bytes {main} [built] 18[webpack-node-externals] external "webpack-node-externals" 42 bytes {main} [built] 19[nodemon] 1.18.4 20[nodemon] to restart at any time, enter `rs` 21[nodemon] watching: build/server.js 22[nodemon] starting `node build/server.js`
By default, Nodemon has been configured to run and watch the first output file of your Webpack build. It has also been set to a 250ms
delay to give Webpack a chance to finish its build before restarting the node server.
1{ 2 script: defaultOutput, 3 watch: defaultOutput, 4 delay: '250' 5}
These settings can be overridden and any other Nodemon configuration properties can be added
1new NodemonNgrokWebpackPlugin({ 2 nodemonConfig: { 3 script: './build/aux.js', // What to run 4 watch: path.resolve('./build'), // What to watch 5 args: ['example'], // Arguments to pass to script 6 verbose: true, // Verbose 7 // etc... 8 }, 9});
By default, Ngrok has been configured to tunnel to port 3000
over the http
protocol
1{ addr: 3000 }
These settings can also be overridden and any other Ngrok configuration properties can be added
1new NodemonNgrokWebpackPlugin({ 2 ngrokConfig: { 3 addr: 8080, // Port to tunnel to 4 authtoken: '4nq9771bPxe8ctg7LKr_2ClH7Y15Zqe4bWLWF9p', // Ngrok auth token 5 subdomain: 'example', // Reserved tunnel name 6 bind_tls: false, // Disable HTTPS 7 // etc... 8 }, 9});
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/6 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
42 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-06-30
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More