v102

CHANGELOG.md

@@ -1,5 +1,29 @@
 # Change Log
 
+## v102
+
+- Support `browser` field of **package.json** to improve compatibility with npm packages in browser. For example, the `webtorrent` package will use `memory-chunk-store` instead of `fs-chunk-store` and exclude built-in modules like `fs`, `net`, `os` and so on. (Close [#450](https://github.com/ije/esm.sh/issues/450))
+  ```json
+  {
+    "name": "webtorrent",
+    "description": "Streaming torrent client",
+    "version": "1.9.6",
+    "browser": {
+      "./lib/server.js": false,
+      "./lib/conn-pool.js": false,
+      "./lib/utp.js": false,
+      "bittorrent-dht/client": false,
+      "fs": false,
+      "fs-chunk-store": "memory-chunk-store",
+      "load-ip-set": false,
+      "net": false,
+      "os": false,
+      "ut_pex": false
+    },
+    ...
+  }
+  ```
+
 ## v101
 
 - Fix `?bundle` mode with illegal paths (close [#476](https://github.com/ije/esm.sh/issues/476)).

README.md

@@ -208,7 +208,7 @@ import unescape from "https://esm.sh/lodash/unescape?no-dts"
 Since we update esm.sh server frequently, sometime we may break packages that work fine previously by mistake, the server will rebuild all modules when the patch pushed. To avoid this, you can **pin** the build version by the `?pin=BUILD_VERSON` query. This will give you an **immutable** cached module.
 
 ```javascript
-import React from "https://esm.sh/[email protected]?pin=v101"
+import React from "https://esm.sh/[email protected]?pin=v102"
 ```
 
 ## Global CDN

server/consts.go

@@ -2,7 +2,7 @@ package server
 
 const (
 	// esm.sh build version
-	VERSION          = 101
+	VERSION          = 102
 	nodejsMinVersion = 16
 	denoStdVersion   = "0.170.0"
 	nodejsLatestLTS  = "16.18.1"