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
👋 Welcome to
@expo/image-utils
A library for image processing functionality in Expo CLI.
It uses sharp for image processing if it's available through a global sharp-cli installation. Otherwise it uses jimp, a Node library with no native dependencies, and warns the user that they may want to install sharp-cli for faster image processing.
Advanced Configuration
This package can be configured using the following environment variables.
EXPO_IMAGE_UTILS_NO_SHARP
When truthy, this will force global sharp-cli resolution methods like isAvailableAsync() and findSharpInstanceAsync() to fail. Other processes can use this to fallback on Jimp for image modifications. By default this is falsy (undefined).
findSharpInstanceAsync() will throw an error if disabled because it shouldn't be invoked if isAvailableAsync() returns false.