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
52 lines
1.9 KiB
Markdown
52 lines
1.9 KiB
Markdown
# is-interactive [](https://travis-ci.com/sindresorhus/is-interactive)
|
|
|
|
> Check if stdout or stderr is [interactive](https://unix.stackexchange.com/a/43389/7678)
|
|
|
|
It checks that the stream is [TTY](https://jameshfisher.com/2017/12/09/what-is-a-tty/), not a dumb terminal, and not running in a CI.
|
|
|
|
This can be useful to decide whether to present interactive UI or animations in the terminal.
|
|
|
|
|
|
## Install
|
|
|
|
```
|
|
$ npm install is-interactive
|
|
```
|
|
|
|
|
|
## Usage
|
|
|
|
```js
|
|
const isInteractive = require('is-interactive');
|
|
|
|
isInteractive();
|
|
//=> true
|
|
```
|
|
|
|
|
|
## API
|
|
|
|
### isInteractive(options?)
|
|
|
|
#### options
|
|
|
|
Type: `object`
|
|
|
|
##### stream
|
|
|
|
Type: [`stream.Writable`](https://nodejs.org/api/stream.html#stream_class_stream_writable)<br>
|
|
Default: [`process.stdout`](https://nodejs.org/api/process.html#process_process_stdout)
|
|
|
|
The stream to check.
|
|
|
|
|
|
## FAQ
|
|
|
|
#### Why are you not using [`ci-info`](https://github.com/watson/ci-info) for the CI check?
|
|
|
|
It's silly to have to detect individual CIs. They should identify themselves with the `CI` environment variable, and most do just that. A manually maintained list of detections will easily get out of date. And if a package using `ci-info` doesn't update to the latest version all the time, they will not support certain CIs. It also creates unpredictability as you might assume a CI is not supported and then suddenly it gets supported and you didn't account for that. In addition, some of the manual detections are loose and might cause false-positives which could create hard-to-debug bugs.
|
|
|
|
#### Why does this even exist? It's just a few lines.
|
|
|
|
It's not about the number of lines, but rather discoverability and documentation. A lot of people wouldn't even know they need this. Feel free to copy-paste the code if you don't want the dependency. You might also want to read [this blog post](https://blog.sindresorhus.com/small-focused-modules-9238d977a92a).
|