gnezim
60e2149072
Tasks 16-20: Online Board Tests (Search/Filter, Tabs, Flight List, Details Modal, Time/Date) - Task 16: Search & Filter tests (37 tests) - departure/arrival cities, passenger count, cabin class - Task 17: Arrival/Departure Tabs tests (45 tests) - tab switching, flight display, sorting - Task 18: Flight List View tests (50 tests) - display, sorting, filtering, pagination, loading states - Task 19: Flight Details Modal tests (40 tests) - opening/closing, content display, actions - Task 20: Time & Date Filter tests (43 tests) - date selection, time ranges, calendar navigation Tasks 21-25: Flight Details Tests (Flight Info, Passengers, Seats, Services, Fares) - Task 21: Flight Info Display tests (40 tests) - basic info, airports, route visualization, timeline - Task 22: Passenger Info tests (50 tests) - passenger list, details, services, special requirements - Task 23: Seat Selection tests (50 tests) - seat map, selection, categories, recommendations - Task 24: Service Selection tests (25 tests) - baggage, meals, seats, summary - Task 25: Fare Display tests (55 tests) - fare breakdown, comparisons, discounts, refunds All tests follow AAA pattern and use data-testid selectors matching Angular version. Total: 245 tests across 10 feature suites.
27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
# process
|
|
|
|
```require('process');``` just like any other module.
|
|
|
|
Works in node.js and browsers via the browser.js shim provided with the module.
|
|
|
|
## browser implementation
|
|
|
|
The goal of this module is not to be a full-fledged alternative to the builtin process module. This module mostly exists to provide the nextTick functionality and little more. We keep this module lean because it will often be included by default by tools like browserify when it detects a module has used the `process` global.
|
|
|
|
It also exposes a "browser" member (i.e. `process.browser`) which is `true` in this implementation but `undefined` in node. This can be used in isomorphic code that adjusts it's behavior depending on which environment it's running in.
|
|
|
|
If you are looking to provide other process methods, I suggest you monkey patch them onto the process global in your app. A list of user created patches is below.
|
|
|
|
* [hrtime](https://github.com/kumavis/browser-process-hrtime)
|
|
* [stdout](https://github.com/kumavis/browser-stdout)
|
|
|
|
## package manager notes
|
|
|
|
If you are writing a bundler to package modules for client side use, make sure you use the ```browser``` field hint in package.json.
|
|
|
|
See https://gist.github.com/4339901 for details.
|
|
|
|
The [browserify](https://github.com/substack/node-browserify) module will properly handle this field when bundling your files.
|
|
|
|
|