e30ae8ed09
- App.tsx: full navigation (Auth stack + Main tabs with 5 screens) - Auth: LoginScreen, RegisterScreen, ForgotPasswordScreen - HomeScreen: dashboard with IoT metrics, weather widget, alerts, quick actions, sensors - MapScreen: interactive map with layer toggles (6 layers) - MarketplaceScreen: categories (6), products (5), search - ChatScreen: AI chat with quick prompts (4), bot responses - ProfileScreen: user info, stats, menu (9 items), logout - AlertsScreen: alert list with severity, acknowledge - SensorsScreen: sensor list with type filters (6 types), search - ZonesScreen: zone cards with stats - SettingsScreen: language picker (FR/EN/ES/DE), privacy, about - Stores: iotStore (sensors, zones, alerts), notificationStore, uiStore + i18n - Hooks: useSensors, useAlerts, useNotifications, useLocation - Components: Card, Button, LoadingSpinner, ErrorBoundary, Header - Services: iotService, notificationService (with axios API client) - Utils: formatters (temp, AQI, noise, dates), validators (email, password, IBAN) - Theme: colors.ts with full design system (Blue Ocean palette) - Ditto: fixed MongoDB connection, new JWT secrets, official gateway image
1.5 KiB
1.5 KiB
set-blocking
set blocking stdio and stderr ensuring that terminal output does not truncate.
const setBlocking = require('set-blocking')
setBlocking(true)
console.log(someLargeStringToOutput)
Historical Context/Word of Warning
This was created as a shim to address the bug discussed in node #6456. This bug crops up on
newer versions of Node.js (0.12+), truncating terminal output.
You should be mindful of the side-effects caused by using set-blocking:
- if your module sets blocking to
true, it will effect other modules consuming your library. In yargs we only callsetBlocking(true)once we already know we are about to callprocess.exit(code). - this patch will not apply to subprocesses spawned with
isTTY = true, this is the defaultspawn()behavior.
License
ISC