rename package to bx

README.md

@@ -1,24 +1,24 @@
-# 🌐 exweb - a browser runner
+# 🌐 bx - a browser runner
 
-With Node.js, Deno or Bun there are so many JavaScript environments to choose from. However, nothing is as good as the browser environment. `exweb` gives you an execution runtime for the browser.
+With Node.js, Deno or Bun there are so many JavaScript environments to choose from. However, nothing is as good as the browser environment. `bx` gives you an execution runtime for the browser.
 
 For example, let's say you have a script like this:
 
 ```js
 console.log(navigator.userAgent)
 ```
 
-With `exweb` you can easily run this script within different browser environments:
+With `bx` you can easily run this script within different browser environments:
 
 ```sh
-> npx exweb ./script.js
+> npx bx ./script.js
 Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36
 ```
 
-You can easily switch browser via the `--browserName` parameter:
+You can easily switch browsers via the `--browserName` parameter:
 
 ```sh
-> npx exweb ./script.js --browserName firefox
+> npx bx ./script.js --browserName firefox
 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:121.0) Gecko/20100101 Firefox/121.0
 ```
 
@@ -31,9 +31,9 @@ It even allows you to run `.html` files, e.g. given this file:
 <b>Hello World!</b>
 ```
 
-Running this with `exweb` results in:
+Running this with `bx` results in:
 
 ```sh
-> npx exweb ./html.html
+> npx bx ./html.html
 Hello World!
 ```

package.json

@@ -1,11 +1,11 @@
 {
-  "name": "exweb",
+  "name": "bx",
   "version": "0.0.3",
   "description": "Command line tool to run JavaScript, TypeScript or HTML files in the browser.",
   "exports": "./dist/index.js",
   "type": "module",
   "bin": {
-    "exweb": "./bin/exweb.js"
+    "bx": "./bin/bx.js"
   },
   "scripts": {
     "test": "vitest --run",