Package Exports
- browser-run
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (browser-run) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
browser-run
The easiest way of running code in a browser environment.
Bundles electronjs by default!
Usage
$ echo "console.log('Hey from ' + location); window.close()" | browser-run
Hey from http://localhost:53227/
$Or use browser-run programmatically:
var run = require('browser-run');
var browser = run();
browser.pipe(process.stdout);
browser.end('console.log(location); window.close()');Example with browserify
$ browserify main.js | browser-runor
var browserify = require('browserify');
var browser = require('browser-run');
browserify('main.js').bundle().pipe(browser()).pipe(process.stdout);CLI
$ browser-run --help
Run JavaScript in a browser.
Write code to stdin and receive console output on stdout.
Usage: browser-run [OPTIONS]
Options:
--browser, -b Browser to use. Always available: electron. Available if installed: chrome, firefox, ie, phantom, safari [default: "electron"]
--port Starts listening on that port and waits for you to open a browser
--static Serve static assets from this directory
--mock Path to code to handle requests for mocking a dynamic back-end
--input Input type. Defaults to 'javascript', can be set to 'html'.
--node Enable nodejs apis in electron
--basedir Set this if you need to require node modules in node mode
--help Print help Custom html file
By using --input html or { input: 'html' } you can provide a custom html file for browser-run to use. Keep in mind though that it always needs to have <script src="/reporter.js"></script> above other script tags so browser-run is able to properly forward your console.logs etc to the terminal.
Dynamic back-end mock
By using --mock mock.js or { mock: 'mock.js'} you can provide a custom server-side implementation and handle all requests that are sent to paths beginning with /mock
mock.js needs to export a function that accepts req and res arguments for handling requests.
Example:
module.exports = function(req,res){
if (req.url === '/mock/echo') {
req.pipe(res)
}
}API
run([opts])
Returns a duplex stream and starts a webserver.
opts can be:
port: If speficied, no browser will be started, so you can point one yourself tohttp://localhost/<port>browser: Browser to use. Defaults toelectron. Available if installed:chromefirefoxiephantomsafari
static: Serve static files from this directorymock: Path to code to handle requests for mocking a dynamic back-endinput: Input type. Defaults tojavascript, can be set tohtml.node: Enable nodejs integration in electronbasedir: Set this if you need to require node modules innodemode
If only an empty string is written to it, an error will be thrown as there is nothing to execute.
If you call window.close() inside the script, the browser will exit.
run#stop()
Stop the underlying webserver.
Headless testing
To use the default electron browser on travis, add this to your travis.yml:
addons:
apt:
packages:
- xvfb
install:
- export DISPLAY=':99.0'
- Xvfb :99 -screen 0 1024x768x24 > /dev/null 2>&1 &
- npm install
For gnu/linux installations without a graphical environment:
$ sudo apt-get install xvfb # or equivalent
$ export DISPLAY=':99.0'
$ Xvfb :99 -screen 0 1024x768x24 > /dev/null 2>&1 &
$ browser-run ...There is also an example docker machine here.
Installation
With npm do
$ npm install browser-run # for library
$ npm install -g browser-run # for cliLicense
(MIT)