Gathering detailed insights and metrics for bs-recipes
Gathering detailed insights and metrics for bs-recipes
Gathering detailed insights and metrics for bs-recipes
Gathering detailed insights and metrics for bs-recipes
bs-logger
Bare simple logger for NodeJS
workbox-recipes
A service worker helper library to manage common request and caching patterns
graphql-ws
Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client
bs-html-injector
Inject only HTML that has changed.
Fully working project examples showing how to use BrowserSync in various ways.
npm install bs-recipes
99
Supply Chain
99.2
Quality
75.7
Maintenance
100
Vulnerability
99.6
License
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
651 Stars
114 Commits
140 Forks
34 Watching
9 Branches
26 Contributors
Updated on 30 Sept 2024
Minified
Minified + Gzipped
JavaScript (74.04%)
HTML (13.57%)
CSS (10.75%)
TypeScript (1.64%)
Cumulative downloads
Total Downloads
Last day
-13.9%
155,666
Compared to previous day
Last week
-5.1%
826,173
Compared to previous week
Last month
30.3%
3,672,135
Compared to previous month
Last year
10.3%
37,597,874
Compared to previous year
There are endless amounts of possible integrations and workflow scenarios when using Browsersync, so this project is an attempt to highlight as many of them as we can, whilst providing full, working examples.
Here's what we have currently...
... each one is a full, working example - just have a look at the readme.md
in each one for installation
instructions.
Spotted an error? Couldn't get one of the examples running? Have your own sweet setup that you want to show off to the world? We'd love to receive your feedback and contributions - so please get in touch! We aim to make this project the canonical source of example projects & code snippets related to running Browsersync.
First thing you should do, is take a look at our simplest example here - this will give you a great head-start on setting up your code.
Then, fork
this repo and clone
your fork down to your local machine. Now create a new folder inside recipes
(note the naming structure). This is where you create your awesome example. You're free to do as you like,
but there are a couple of rules you'll need to follow to ensure the project can build.
Required Files
package.json
(see below for requirements)app.js
(or any JS file showing the example)./app
directory. Always include the minimum HTML, JS & CSS needed to prove your example.Do NOT include
readme.md
(this is created dynamically for you)start command: For consistency, ensure your example can be run with the command npm start
. To
do this, you just need to provide something along these lines:
1"scripts": { 2 "start": "node app.js" 3},
main file: We inline your main Javascript file into the readme.md
, so
don't miss this field.
1"main": "app.js" // or gulpfile.js etc
description: We use this as the Title. So make it short and descriptive, such as
1"description": "Server example"
After you've added your example in the recipes folder, return to the root and run
1npm install && npm run build
This will install Crossbow.js and compile the project. Commit everything that has changed and push it up to your fork. Send a Pull Request when you're ready, or if you'd like us to have a look over your code before that, just ping us twitter and we'll take a look!
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
Found 5/18 approved changesets -- score normalized to 2
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
license file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
109 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-25
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