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
27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
# resolve package - session notes
|
|
|
|
## Versioning
|
|
- Manual versioning only - do NOT use `npm version`
|
|
- Edit package.json version directly, commit with message `v{version}`, then create annotated tag
|
|
- Changelog lives in git tag annotations, not a separate file
|
|
- Tag format: `git tag -a v{version} -m "{changelog}"`
|
|
|
|
## Code style
|
|
- `__proto__: null` on ALL object literals (prototype pollution protection)
|
|
- `.slice()` not `.substring()`
|
|
- One exported function per file
|
|
- Move nested/inner functions to module level when feasible
|
|
- Prefer non-hoisted declarations (function declarations at module level, not expressions)
|
|
- No mutation - copy objects instead of modifying inputs
|
|
|
|
## Testing
|
|
- `test/list-exports` is a git submodule with sparse checkout
|
|
- Tests should cover ALL entrypoints from fixtures, not just `'.'` subpaths
|
|
- Use `extensions: ['.js', '.json']` when testing exports resolution
|
|
|
|
## exports field implementation
|
|
- Uses `node-exports-info` for category semantics
|
|
- Categories: pre-exports, broken, conditions, patterns, pattern-trailers, current
|
|
- `exportsCategory` option or `engines: true` to auto-detect from consumer's engines.node
|
|
- Self-reference resolution respects node_modules boundaries
|