bunny.net - npm Package Compare versions

Comparing version 0.0.0 to 1.0.0

package.json

 {
   "name": "bunny.net",
-  "version": "0.0.0",
-  "description": "",
-  "main": "index.js",
+  "version": "1.0.0",
+  "author": "Samuel Kopp (https://samuelkopp.de)",
+  "license": "Apache-2.0",
+  "description": "JavaScript SDK for 🐇 bunny.net",
+  "funding": "https://github.com/sponsors/boywithkeyboard",
+  "repository": "github:boywithkeyboard/bunny.net",
+  "keywords": [
+    "bunny",
+    "bunny.net",
+    "sdk",
+    "dns",
+    "cdn",
+    "edge storage"
+  ],
+  "main": "./build/index.cjs",
+  "module": "./build/index.mjs",
+  "types": "./build/index.d.ts",
+  "files": [
+    "./build"
+  ],
+  "exports": {
+    ".": {
+      "import": {
+        "default": "./build/index.mjs",
+        "types": "./build/index.d.ts"
+      },
+      "require": {
+        "default": "./build/index.cjs",
+        "types": "./build/index.d.ts"
+      }
+    }
+  },
   "scripts": {
-    "test": "echo \"Error: no test specified\" && exit 1"
+    "build:cjs": "esbuild src/index.ts --bundle --minify --format=cjs --target=es2022 --outfile=build/index.cjs",
+    "build:esm": "esbuild src/index.ts --bundle --minify --format=esm --target=es2022 --outfile=build/index.mjs",
+    "build": "rimraf build && tsc && npm run build:cjs && npm run build:esm",
+    "prepublishOnly": "npm run build"
   },
-  "author": "",
-  "license": "ISC"
+  "devDependencies": {
+    "@types/node": "^20.11.24",
+    "esbuild": "^0.20.1",
+    "rimraf": "^5.0.5",
+    "typescript": "^5.3.3"
+  },
+  "engines": {
+    "node": ">=18"
+  }
 }

New alerts

Major refactor

Supply chain risk

Package 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

Network access

Supply chain risk

This module accesses the network.

Found 1 instance in 1 package

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Fixed alerts

Empty package

Supply chain risk

Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.

Found 1 instance in 1 package

No README

Quality

Package does not have a README. This may indicate a failed publish or a low quality package.

Found 1 instance in 1 package

No contributors or author data

Maintenance

Package does not specify a list of contributors or an author in package.json.

Found 1 instance in 1 package

No bug tracker

Maintenance

Package does not have a linked bug tracker in package.json.

Found 1 instance in 1 package

No repository

Supply chain risk

Package does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.

Found 1 instance in 1 package

No tests

Quality

Package does not have any tests. This is a strong signal of a poorly maintained or low quality package.

Found 1 instance in 1 package

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Found 1 instance in 1 package

No website

Quality

Package does not have a website.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

53492

increased by25993.66%

Number of package files

17

increased by1600%

Lines of code

178

increased byInfinity%

Number of low maintenance alerts

0

decreased by-100%

Number of low quality alerts

0

decreased by-100%

Number of medium quality alerts

1

decreased by-50%

Number of lines in readme file

48

increased byInfinity%

Number of low supply chain risk alerts

0

decreased by-100%

Worsened metrics

Dev dependency count

4

increased byInfinity%

Number of medium supply chain risk alerts

14

increased by1300%

No dependency changes