Skip to main content
This section contains deprecated documentation for the old npm package approach (@replyke/comments-threaded-react-js, @replyke/comments-social-react-js).These packages still work but are no longer recommended. We’ve moved to a CLI-based component distribution system that gives you full source code ownership and unlimited customization.

​
Legacy Component Documentation

This section preserves documentation for developers still using the old npm packages.

​
Why These Are Deprecated

The npm package approach had significant limitations:
  • Limited customization: Only surfaces exposed via styleCallbacks could be styled
  • Complex configuration: Dozens of callback functions required for styling
  • Hidden code: Components lived in node_modules, not visible or editable
  • Version lock-in: Updates could break your implementation
  • No layout control: Couldn’t rearrange, remove, or add UI elements
We strongly recommend migrating to the new CLI-based approach:

Migration Guide

Complete step-by-step migration guide

New Components Overview

Learn about the CLI-based system

Quick Start

Get started with CLI in under 5 minutes

Benefits

Why CLI is better than npm packages

​
Legacy Documentation Index

If you need to reference the old npm package documentation:

​
Social Comments (Legacy)

​
Threaded Comments (Legacy)

​
Advanced (Legacy)

​
npm Package Names

For reference, the legacy packages were: React (Web):
  • @replyke/comments-threaded-react-js
  • @replyke/comments-social-react-js
React Native:
  • @replyke/comments-social-react-native

​
Support Status

PackageStatusSupport
@replyke/comments-threaded-react-jsDeprecatedSecurity fixes only
@replyke/comments-social-react-jsDeprecatedSecurity fixes only
@replyke/comments-social-react-nativeDeprecatedSecurity fixes only
New features and improvements will only be added to CLI components.

​
Still Have Questions?

The CLI approach gives you:
  • Full source code ownership
  • Unlimited customization (not just styleCallbacks)
  • Simpler API (no complex props)
  • Better version control
  • Ability to modify layout and functionality
See the Migration Guide for full details.
Legacy packages will receive security fixes only. No new features or improvements will be added.We recommend migrating when convenient, but there’s no immediate deadline.
Yes. Your existing entities, comments, votes, and user data work seamlessly with CLI components. The backend is unchanged.
Migration is straightforward:
  1. Install CLI components
  2. Update imports
  3. Remove styleCallbacks prop
  4. Apply customizations in source files
Most projects can migrate in under 30 minutes.See the Migration Guide.

​
Get Started with CLI

Ready to migrate?
1

Read the Migration Guide

Migration Guide - Complete walkthrough
2

Install CLI Components

npx @replyke/cli init
npx @replyke/cli add comments-threaded
3

Test Side-by-Side

Test the CLI version alongside your npm version before fully migrating.
4

Apply Customizations

Use the Mapping Guide to apply your old styleCallbacks customizations.
Need help migrating? Join our Discord community or open an issue on GitHub.