
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
grunt-browser-output
Advanced tools
Show grunt errors in a popup window in your browser.
This plugin will mirror the Grunt console output in a browser window when a plugin shows warnings or errors. The motivation is to avoid having to toggle back to a terminal window to see errors (ex. JSHint warnings) during a grunt/watch/livereload session.
Only works in modern browsers with WebSocket support.
npm install grunt-browser-output --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-browser-output');
Important: Using this plugin with grunt-contrib-watch
and livereload
requires grunt-contrib-watch
version 0.6.0
or higher and you must configure livereloadOnError = false.
In your project's Gruntfile, add a section named browser_output
to the data object passed into grunt.initConfig()
.
grunt.initConfig({
browser_output: {
options: { //all options are optional
port: 37901 //default is 37901
}
},
})
Add browser_output
before your watch
task.
grunt.registerTask('serve', ['browser_output','connect', 'watch']);
Finally, add the following script tag to your web page:
<script src="node_modules/grunt-browser-output/client.js"></script>
If you run your site over HTTPS, you'll likely want to configure this task to also use HTTPS. Change the task config:
grunt.initConfig({
browser_output: {
options: {
ssl: true,
key: grunt.file.read('path/to/server.key'),
cert: grunt.file.read('path/to/server.crt')
}
},
})
And in your index.html add put ?ssl=true
on the end of the client.js script tag:
<script src="node_modules/grunt-browser-output/client.js?ssl=true"></script>
FAQs
Redirect grunt output to the browser.
We found that grunt-browser-output demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
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
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.