From 40fe516ae5830cb4d5457571960478d4bd508a7c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E2=80=9Ctalatkuyuk=E2=80=9D?= <“talatkuyuk@gmail.com”>
Date: Fri, 10 Jan 2025 00:31:47 +0300
Subject: [PATCH] v1.0.4

---
 README.md    | 7 +++++++
 package.json | 6 +++---
 2 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index d3e7548..d857926 100644
--- a/README.md
+++ b/README.md
@@ -8,6 +8,13 @@
 [![typescript][badge-typescript]][typescript-url]
 [![License][badge-license]][github-license-url]
 
+> [!IMPORTANT]
+> **If you are using `react18`, use ver.1 of `next-mdx-remote-client`, currently v1.0.4**
+>
+> **If you are using `react19`, use ver.2 of `next-mdx-remote-client`, currently v2.0.0**
+>
+> *The both serve the same features and APIs. I am going to maintain both.*
+
 The **`next-mdx-remote-client`** is a wrapper of **`@mdx-js/mdx`** for **`nextjs`** applications in order to load MDX content. It is a fork of **`next-mdx-remote`**.
 
 See some blog applications in which **`next-mdx-remote-client`** is used:
diff --git a/package.json b/package.json
index 429753d..1f3fbce 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "next-mdx-remote-client",
   "description": "A wrapper of the `@mdx-js/mdx` for the `nextjs` applications in order to load MDX content. It is a fork of `next-mdx-remote`.",
-  "version": "1.0.3",
+  "version": "1.0.4",
   "main": "./dist/csr/index.js",
   "types": "./dist/csr/index.d.ts",
   "type": "module",
@@ -109,8 +109,8 @@
     "vitest": "^2.1.8"
   },
   "peerDependencies": {
-    "react": "^18.3",
-    "react-dom": "^18.3"
+    "react": ">= 18.3.0 < 19.0.0",
+    "react-dom": ">= 18.3.0 < 19.0.0"
   },
   "engines": {
     "node": ">=18.18.0"