refactor: Reconnect banner Blaze -> native React (drops findDOMNode)
Reconnect rendered the Blaze meteorStatus template via gadicc:blaze-react-component, whose bridge uses the deprecated findDOMNode (warned on every page since it's always mounted). Reimplemented natively with useTracker(Meteor.status) + a countdown effect, same behaviour and reusing 255kb:meteor-status's .meteor-status CSS. Also dropped the dead Blaze import from App.js. Remaining findDOMNode warnings are third-party only: react-progress-bar.js (LoadingBar) and Status.js's Blaze serverFacts (/status admin page). Browser-verified home renders, no banner while connected, no new errors. REST smoke byte-identical.
This commit is contained in:
parent
229b2cb233
commit
258723ea72
2 changed files with 41 additions and 32 deletions
|
|
@ -9,8 +9,6 @@ import { I18nextProvider } from 'react-i18next';
|
|||
import { Helmet } from 'react-helmet-async';
|
||||
import { Meteor } from 'meteor/meteor';
|
||||
import { withTracker } from 'meteor/react-meteor-data';
|
||||
// https://github.com/gadicc/meteor-blaze-react-component/
|
||||
import Blaze from 'meteor/gadicc:blaze-react-component';
|
||||
// i18n
|
||||
import i18n, { i18nReady } from '/imports/startup/client/i18n';
|
||||
import '/imports/startup/client/meta';
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue