-
-
Notifications
You must be signed in to change notification settings - Fork 25
feat: switch to @bitsocial/bitsocial-react-hooks 0.1.2 and rebrand subplebbit → community #816
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c8ce0c8
chore(deps): switch to @bitsocial/bitsocial-react-hooks@0.1.2
tomcasaburi 8d017a1
refactor: switch import scope from @bitsocialnet to @bitsocial
tomcasaburi 309c553
refactor: rename subplebbit -> community across seedit
tomcasaburi c5cb66e
refactor: rename subplebbit → community throughout UI layer
tomcasaburi c5348a0
fix(community-rebrand): address Cursor Bugbot and CodeRabbit findings
tomcasaburi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: bitsocialnet/seedit
Length of output: 4756
🌐 Web query:
react-i18next 16 breaking changes from v13💡 Result:
The primary breaking change when upgrading react-i18next from v13 to v16 is the required upgrade of the peer dependency i18next from >=v23.0.1 (required by v13.0.0) to >=v25.5.2+ (for v16.x, later bumped to >=25.10.9 in v16.6.6). This i18next upgrade introduces several breaking changes that affect react-i18next usage. Key i18next breaking changes impacting react-i18next (from v23 to v25+): - Build process changes: dist/es -> dist/esm, dist/commonjs -> dist/cjs (bundled files instead of individual). - TypeScript typing updates requiring corresponding react-i18next type changes. - Later v25+ changes like peer dep alignments for TransSelector types. react-i18next v16.0.0 itself notes "major upgrade i18next dep to address 1865" with no explicit API breaks listed in its changelog. Post-v16 releases (16.3.0+) include minor fixes like i18n wrappers for React Compiler/memo compatibility and Trans defaultValue handling, but these are not flagged as breaking. Migration steps: 1. Upgrade i18next to >=25.10.9 alongside react-i18next ^16.6.6. 2. Review i18next migration guide for v23->v25: https://www.i18next.com/misc/migration-guide (covers build changes, no major config/API breaks). 3. Check Trans component usage for type errors with selectors (fixed by matching peer deps). 4. Test for bundle/build issues due to new dist structure. 5. No direct react-i18next API changes; mostly transparent via i18next dep.
Citations:
🌐 Web query:
@vitejs/plugin-react 6 breaking changes💡 Result:
The breaking changes in
@vitejs/plugin-reactv6.0.0 (released March 12, 2026) are: 1. Remove Babel Related Features: Babel is no longer a dependency. The babel option in the plugin config is removed. Users needing Babel must add@rolldown/plugin-babelseparately. For React Compiler, use reactCompilerPreset with it. Example migration: - react({ babel: { plugins: [...] } }) + react, babel({ plugins: [...] }) 2. Drop Vite 7 and below support: Requires Vite 8+. Upgrade if using older Vite. 3. Use Oxc for React Refresh Transform in rolldown-vite:@vitejs/plugin-react-oxcis deprecated; disableOxcRecommendation option removed. 4. react and react-dom no longer added to resolve.dedupe automatically. 5. Remove old babel-plugin-react-compiler support requiring runtimeModule option: Use newer versions supporting target option. v6.0.1 (March 13, 2026) is a patch expanding@rolldown/plugin-babelpeer deps, no new breaks.Citations:
Fix vite.config.ts Babel configuration before upgrading
@vitejs/plugin-reactto v6.The package.json versions are pinned correctly. However, the current vite.config.ts will break after the upgrade:
@vitejs/plugin-reactv6.0.0 removed thebabeloption from the plugin configuration. The config currently uses:This pattern is no longer supported. You must:
@rolldown/plugin-babelas a dependency@rolldown/plugin-babelinstead of via thereact()pluginSee the migration guide.
The i18next 23 → 25 and react-i18next 13 → 16 upgrades are safe:
fallbackLnganddefaultNSare already explicitly configured in src/lib/init-translations.ts, and no implicit defaults are being silently relied upon. The react-i18next v16 breaking changes are primarily driven by the i18next peer dependency alignment, with no direct API breaks in react-i18next itself. Complete manual UI testing before merge as already planned.🤖 Prompt for AI Agents