rehackt

library0.1.0jsnpmunverified

Rehackt is an advanced utility library designed for JavaScript/TypeScript library developers working with Next.js and React Server Components (RSC). Its primary function is to invisibly wrap the `react` package, allowing shared imports that contain React hooks (e.g., `useState`, `useEffect`) to be used in server-side Next.js codebases without triggering static analysis errors from the Next.js build process. This prevents common build failures where RSC compilers erroneously flag client-side hooks in modules that are not intended for server-side execution but are imported into a server context. The package is currently at version `0.1.0` and appears to have an active, albeit niche, release cadence driven by changes in React's internal APIs related to RSC. Its key differentiator is solving a specific interop problem for libraries that need to expose both client and server functionalities and manage the RSC static analysis rules without extensive code splitting or dual packages. It does not enable actual hook execution on the server; it only circumvents build-time errors.

web-framework

npm install rehackt

github ↗package ↗

INSTALL

IMPORT

SIG · REHACKT

rehackt

web-frameworkjavascriptv0.1.0

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

useState

✓ import { useState } from 'rehackt';

✗ const { useState } = require('rehackt');

Rehackt is an ESM-first library. Use named imports for individual hooks and other React exports.

useEffect

✓ import { useEffect } from 'rehackt';

✗ import React from 'rehackt'; React.useEffect(...)

Import any React hook or utility you would normally get from 'react' directly from 'rehackt'. Rehackt re-exports everything from 'react'.

Fragment

✓ import { Fragment } from 'rehackt';

✗ import { Fragment } from 'react';

While importing from 'react' is generally correct, using 'rehackt' ensures consistent behavior for libraries that need to hide client-side dependencies from the RSC compiler even for basic React exports.

Demonstrates replacing `import {useState} from "react"` with `import {useState} from "rehackt"` in a shared module to prevent React Server Components build errors when imported into a server-only context.

import { useState } from "rehackt"; export const data = { useForm: <T>(val: T) => { useState(val) }, name: "server" } // This shared module can now be imported into a server-side file (e.g., a Next.js server action) // without triggering a React Server Components error, even though it contains a client-side hook reference. // For example, in 'action.ts': // "use server" // import { data } from './shared-code'; // export default async function someAction() { // return 'Hello ' + data.name; // }

Debug

Known issues

gotchaRehackt is an advanced tool primarily intended for library developers to solve specific interop issues with Next.js Server Components. It is not generally recommended for application-level code.

fix

Only use this package if you are developing a library that needs to share code with client-side hooks across client and server boundaries in a Next.js application without triggering RSC static analysis errors.

affects: >=0.0.1

breakingReact 19 Canary renamed internal fields `__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED` to `__CLIENT_INTERNALS_DO_NOT_USE_OR_WARN_USERS_THEY_CANNOT_UPGRADE` and `__SERVER_INTERNALS_DO_NOT_USE_OR_WARN_USERS_THEY_CANNOT_UPGRADE`. Older versions of `rehackt` might break when used with React 19 Canary.

fix

Upgrade to `rehackt@0.1.0` or newer to ensure compatibility with React 19 Canary, which adds `undefined` exports for potentially missing React internals.

affects: <0.1.0

gotchaUsing `rehackt` does NOT enable the usage of React hooks (like `useState` or `useEffect`) in server-only code. It solely prevents build-time errors caused by static analysis when a module containing a hook reference is imported into a server context.

fix

Ensure that any code calling actual React hooks is still executed in a client component, marked with `'use client'`, as per standard React and Next.js guidelines.

affects: >=0.0.1

Errors

Common errors & fixes

ReactServerComponentsError: You're importing a component that needs useState. It only works in a Client Component but none of its parents are marked with "use client", so they're Server Components by default.

A module containing a client-side React hook (e.g., `useState`) is being imported into a server-side file or a module that is transitively imported by a server-side file, triggering a static analysis error by the Next.js build process.

fix

Replace the import of client-side React hooks (e.g., `import { useState } from "react";`) with `import { useState } from "rehackt";` in the shared module.

Upgrade

Version history

0.1.0latest on npm

Audit

Dependencies

reactrequiredPeer dependency, as rehackt acts as a wrapper/proxy for React's exports.

@types/reactoptionalPeer dependency for TypeScript type definitions compatible with React.

Agent activity

4 hits · last 30 days

node

Resources

githubhttps://github.com/phryneas/rehackt ↗

packagehttps://www.npmjs.com/package/rehackt ↗