V6

.eslintrc.json

@@ -90,6 +90,8 @@
     "@typescript-eslint/ban-ts-comment": "off",
     "dot-notation": "off",
     "no-shadow": "off",
-    "@typescript-eslint/no-shadow": "error"
+    "@typescript-eslint/no-shadow": "error",
+    "react-hooks/rules-of-hooks": "error",
+    "react-hooks/exhaustive-deps": "warn"
   }
 }

.github/FUNDING.yml

@@ -1,9 +1,9 @@
 # These are supported funding model platforms
 
-github: [gabrieljablonski, danielbarion] # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+github: [danielbarion, gabrieljablonski] # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
 patreon: # Replace with a single Patreon username
 open_collective: # Replace with a single Open Collective username
-ko_fi: # Replace with a single Ko-fi username
+ko_fi: danielbarion # Replace with a single Ko-fi username
 tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
 community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
 liberapay: # Replace with a single Liberapay username

.github/workflows/beta-release.yaml

@@ -17,10 +17,10 @@ jobs:
       issues: write
       pull-requests: write
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
         with:
           ref: ${{ github.head_ref }}
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v5
         with:
           node-version: '24.14.0'
           registry-url: 'https://registry.npmjs.org'
@@ -52,7 +52,7 @@ jobs:
           name: npm-debug-logs
           path: /home/runner/.npm/_logs
 
-      - uses: actions/github-script@v6
+      - uses: actions/github-script@v8
         with:
           script: |
             github.rest.issues.createComment({

.github/workflows/lint.yaml

@@ -7,29 +7,37 @@ jobs:
   lint:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/checkout@v5
+      - uses: actions/setup-node@v5
+        with:
+          node-version: 20
 
       - name: Install dev dependencies
         run: yarn install
 
       - name: ESLint
         run: yarn run eslint
 
-  test:
+  react-versions:
     needs: lint
     strategy:
       matrix:
-        version: [16, 18, 20]
+        react-version: ['16.14', '17', '18', '19']
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/checkout@v5
+      - uses: actions/setup-node@v5
         with:
-          node-version: ${{ matrix.version }}
+          node-version: 20
 
       - name: Install dev dependencies
         run: yarn install
 
+      - name: Configure React version
+        run: yarn ci:react-version ${{ matrix.react-version }}
+
       - name: Run tests
-        run: yarn run test
+        run: yarn test --runInBand
+
+      - name: Generate types
+        run: npm run types

.gitignore

@@ -30,6 +30,9 @@
 
 ## other
 yarn-error.log
+/benchmarks/results/*.json
+/benchmarks/results/*.md
+/benchmarks/.cache/
 
 # push to github
 !.babelrc
@@ -38,4 +41,3 @@ yarn-error.log
 
 # yalc
 /.yalc
-

.husky/pre-commit

@@ -1,6 +1,3 @@
-#!/bin/sh
-. "$(dirname "$0")/_/husky.sh"
-
 npm run eslint
 # npm run stylelint
 npm run prettier

.npmignore

@@ -30,7 +30,7 @@ rollup-plugins/
 // misc files
 bundlesize.config.json
 prebuild.js
-jest.config.ts
+jest.config.mjs
 
 // bundler - rollup
 rollup.config.dev.js

README.md

@@ -42,6 +42,32 @@ or
 yarn add react-tooltip
 ```
 
+## React Compatibility
+
+`react-tooltip` supports React `16.14.0` and newer through peer dependencies, including React 17, 18, and 19.
+
+The project is currently validated against React 19, but the published package remains compatible with older supported React versions.
+
+| React version | Supported |
+| ------------- | --------- |
+| 16.14+        | Yes       |
+| 17.x          | Yes       |
+| 18.x          | Yes       |
+| 19.x          | Yes       |
+
+## Server Components
+
+`react-tooltip` is a client-side library. It uses hooks, DOM observers, browser events, and layout measurement, so the tooltip component itself must run inside a client component boundary.
+
+This works well in frameworks such as Next.js with Server Components, but you should render `<Tooltip />` from a client component and attach your tooltip attributes or selectors from elements rendered under that client boundary.
+
+If you are using React Server Components, the practical rule is simple:
+
+- server components can render the anchor markup
+- client components should render and control `react-tooltip`
+
+In Next.js, the usual pattern is to export the tooltip from a small wrapper file marked with `'use client'`.
+
 ## Sponsors
 
 ### Gold Sponsors 🌟