v109

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Change Log
 
+## v109
+
+- Ignore `?external` option for stable builds
+- Fix `react/jsx-runtime` bundles `react` module
+- Remove alias export resolving (close [#530](https://github.com/ije/esm.sh/issues/530))
+
 ## v108
 
 - Add `denonext` target to use [deno 1.31 node compatibility layer](https://deno.com/blog/v1.31#compatibility-layer-is-now-part-of-the-runtime)

README.md

@@ -71,8 +71,8 @@ Import maps supports [**trailing slash**](https://github.com/WICG/import-maps#pa
 ```json
 {
   "imports": {
-    "react-dom": "https://esm.sh/[email protected]?pin=v108&dev",
-    "react-dom/": "https://esm.sh/[email protected]&pin=v108&dev/",
+    "react-dom": "https://esm.sh/[email protected]?pin=v109&dev",
+    "react-dom/": "https://esm.sh/[email protected]&pin=v109&dev/",
   }
 }
 ```
@@ -242,9 +242,9 @@ To ensure stable and consistent behavior, you may want to pin the build version
 The `?pin` query allows you to specify a specific build version of a module, which is an **immutable** cached version stored on the esm.sh CDN.
 
 ```javascript
-import React from "https://esm.sh/react-dom?pin=v108"
+import React from "https://esm.sh/react-dom?pin=v109"
 // or use version prefix
-import React from "https://esm.sh/v108/react-dom"
+import React from "https://esm.sh/v109/react-dom"
 ```
 
 By using the `?pin` query in the import statement, you can rest assured that the version of the module you're using will not change, even if updates are pushed to the esm.sh server. This helps ensure the stability and reliability of your application.

server/consts.go

@@ -2,7 +2,7 @@ package server
 
 const (
 	// esm.sh build version
-	VERSION          = 108
+	VERSION          = 109
 	nodejsMinVersion = 16
 	denoStdVersion   = "0.177.0"
 	nodejsLatestLTS  = "16.19.1"