meteor3: bcrypt 1.0.3 -> 5.1.1
The 1.x native binding was built for another Node ABI and failed to load (accounts-password silently used the pure-JS fallback) and 1.x does not compile on Node 22, which would break the Docker image build. 5.1.1 ships prebuilt Node-22 binaries and loads natively. Boot + REST smoke green.
This commit is contained in:
parent
1f1f5c697d
commit
713f1346e7
3 changed files with 466 additions and 1310 deletions
|
|
@ -301,8 +301,9 @@ MONGO_CONTAINER=tcef-mongo7 MONGO_SHELL=mongosh MONGO_PORT=27019 ./smoke/smoke.s
|
|||
|
||||
| Dep | From | Target | Status |
|
||||
|---|---|---|---|
|
||||
| React / react-dom | 16.0 | 18 | **debt** — deferred; ancient react-* libs (react-bootstrap 0.31, reactstrap 5-alpha, react-leaflet 1.8) break on 18. React 16 works through Meteor 2.x/3.x. Own front-end project. |
|
||||
| Server async/await | Fibers | `*Async` APIs | **pending** — prep for 3.x; 2.x still runs on Fibers so not yet required. |
|
||||
| React / react-dom | 16.0 | 18 | ✅ done — 18.3.1 + createRoot; ancient react-* libs work on 18 via legacy context (die on 19, debt). |
|
||||
| Server async/await | Fibers | `*Async` APIs | ✅ done — REST, publications, methods, startup and migrations all on `*Async`. |
|
||||
| bcrypt | 1.0.3 (broken binding) | 5.x | ✅ done — 1.0.3 didn't load on Node 22 (accounts-password silently fell back to pure JS) and wouldn't compile in the Docker build; 5.1.1 ships Node-22 prebuilds. |
|
||||
| raven / flowkey:raven | 2.4 | @sentry/node + @sentry/react | debt — DSN off until GlitchTip/Sentry back (sentry.comunes.org dead → harmless boot-log timeout noise) |
|
||||
| nodemailer | 4 | 6+ | pending |
|
||||
| Babel | 7 beta | 7 stable | ✅ done (escala 1) |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue