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
59 lines
1.6 KiB
Markdown
59 lines
1.6 KiB
Markdown
# unicode-canonical-property-names-ecmascript [](https://www.npmjs.com/package/unicode-canonical-property-names-ecmascript)
|
|
|
|
_unicode-canonical-property-names-ecmascript_ exports the set of canonical Unicode property names that are supported in [ECMAScript RegExp property escapes](https://github.com/tc39/proposal-regexp-unicode-property-escapes).
|
|
|
|
## Installation
|
|
|
|
To use _unicode-canonical-property-names-ecmascript_, install it as a dependency via [npm](https://www.npmjs.com/):
|
|
|
|
```bash
|
|
$ npm install unicode-canonical-property-names-ecmascript
|
|
```
|
|
|
|
Then, `require` it:
|
|
|
|
```js
|
|
const properties = require('unicode-canonical-property-names-ecmascript');
|
|
```
|
|
|
|
## Example
|
|
|
|
```js
|
|
properties.has('ID_Start');
|
|
// → true
|
|
properties.has('IDS');
|
|
// → false
|
|
```
|
|
|
|
## For maintainers
|
|
|
|
### How to publish a new release
|
|
|
|
1. On the `main` branch, bump the version number in `package.json`:
|
|
|
|
```sh
|
|
npm version patch -m 'Release v%s'
|
|
```
|
|
|
|
Instead of `patch`, use `minor` or `major` [as needed](https://semver.org/).
|
|
|
|
Note that this produces a Git commit + tag.
|
|
|
|
1. Push the release commit and tag:
|
|
|
|
```sh
|
|
git push && git push --tags
|
|
```
|
|
|
|
Our CI then automatically publishes the new release to npm.
|
|
|
|
## Author
|
|
|
|
| [](https://twitter.com/mathias "Follow @mathias on Twitter") |
|
|
|---|
|
|
| [Mathias Bynens](https://mathiasbynens.be/) |
|
|
|
|
## License
|
|
|
|
_unicode-canonical-property-names-ecmascript_ is available under the [MIT](https://mths.be/mit) license.
|