From 4431c52afca42e0e15f68fae0360878ee1a9b25e Mon Sep 17 00:00:00 2001
From: X <i@jex.me>
Date: Sun, 29 Jan 2023 01:46:13 +0800
Subject: [PATCH] v106

---
 CHANGELOG.md     | 4 ++++
 README.md        | 2 +-
 server/consts.go | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index d46bf305b..7890b5b0a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,9 @@
 # Change Log
 
+## v106
+
+- Just fix fake module export names resolving (close [#510](https://github.com/ije/esm.sh/issues/510))
+
 ## v105
 
 - Check types which is not defined in `package.json`
diff --git a/README.md b/README.md
index ca00c95eb..016ecf73e 100644
--- a/README.md
+++ b/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/react@17.0.2?pin=v105"
+import React from "https://esm.sh/react@17.0.2?pin=v106"
 ```
 
 ## Global CDN
diff --git a/server/consts.go b/server/consts.go
index edb5218ce..7a46c3e5d 100644
--- a/server/consts.go
+++ b/server/consts.go
@@ -2,7 +2,7 @@ package server
 
 const (
 	// esm.sh build version
-	VERSION          = 105
+	VERSION          = 106
 	nodejsMinVersion = 16
 	denoStdVersion   = "0.175.0"
 	nodejsLatestLTS  = "16.18.1"