bff - npm Package Compare versions
Comparing version
| { | ||
| "name": "bff", | ||
| "version": "0.0.1", | ||
| "version": "0.1.1", | ||
| "description": "Browserify Friend - it's as if browserify was built into the browser.", | ||
@@ -10,3 +10,3 @@ "dependencies": { | ||
| }, | ||
| "bin": "server.js", | ||
| "bin": "cli.js", | ||
| "devDependencies": {}, | ||
@@ -21,2 +21,7 @@ "scripts": { | ||
| ], | ||
| "files": [ | ||
| "cli.js", | ||
| "lib", | ||
| "README.md" | ||
| ], | ||
| "author": "Toby Ho", | ||
@@ -23,0 +28,0 @@ "license": "MIT", |
| Browserify Friend | ||
| ====================== | ||
| Browserify Friend (BFF) makes it as if browserify was built into the browser. | ||
| Browserify Friend (BFF) - it is as if browserify was built into the browser. | ||
@@ -10,9 +10,45 @@ ## Install | ||
| ## Usage | ||
| ## Development Server | ||
| In a directory run: | ||
| > bff | ||
| Serving the contents of /Users/airportyh/Home/Code/bff on port 3000. | ||
| > bff server | ||
| Serving contents on port 3000. | ||
| This will start a static file web server on port 3000 except that Javascript files will automatically get browserified. | ||
| ## Build the Site | ||
| In the same directory run: | ||
| > bff build | ||
| Successfully browserified your site in 'build'. | ||
| Now your site has been browserified within the `build` directory and it can be served by a static web server. | ||
| ## Example | ||
| To try this out, start in a new empty directory. Let's install `domify` a library to convert an html string into a DOM element | ||
| npm install domify | ||
| make an `index.html` file with just this | ||
| <body> | ||
| <script src="index.js"></script> | ||
| </body> | ||
| Make an `index.js` | ||
| var domify = require('domify') | ||
| document.body.appendChild(domify('<h1>Hello World with Browserify!</h1>')) | ||
| Start the bff server | ||
| bff server | ||
| Navigate to `http://localhost:3000` and see it work. | ||
New alerts
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Fixed alerts
Network access
Supply chain riskThis module accesses the network.
Found 1 instance in 1 package
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
Uses eval
Supply chain riskPackage uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Found 1 instance in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 1 instance in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
Mixed license
License(Experimental) Package contains multiple licenses.
Found 1 instance in 1 package
Improved metrics
- Number of low license alerts
0
-100%- Number of lines in readme file
54
200%- Number of low supply chain risk alerts
2
-98.02%- Number of medium supply chain risk alerts
2
-85.71%Worsened metrics
- Total package byte prevSize
7187
-99.37%- Number of package files
6
-97.4%- Lines of code
201
-98.81%