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.
2.6 KiB
arch 
Better os.arch() for node and the browser -- detect OS architecture
This module is used by WebTorrent Desktop to determine if the user is on a 32-bit vs. 64-bit operating system to offer the right app installer.
In Node.js, the os.arch() method (and process.arch property) returns a string
identifying the operating system CPU architecture for which the Node.js binary
was compiled.
This is not the same as the operating system CPU architecture. For example,
you can run Node.js 32-bit on a 64-bit OS. In that situation, os.arch() will
return a misleading 'x86' (32-bit) value, instead of 'x64' (64-bit).
Use this package to get the actual operating system CPU architecture.
BONUS: This package works in the browser too.
install
npm install arch
usage
var arch = require('arch')
console.log(arch()) // always returns 'x64' or 'x86'
In the browser, there is no spec that defines where this information lives, so we
check all known locations including navigator.userAgent, navigator.platform,
and navigator.cpuClass to make a best guess.
If there is no affirmative indication that the architecture is 64-bit, then 32-bit will be assumed. This makes this package perfect for determining what installer executable to offer to desktop app users. If there is ambiguity, then the user will get the 32-bit installer, which will work fine even for a user with a 64-bit OS.
For reference, x64 means 64-bit and x86 means 32-bit.
Here is some history behind these naming conventions:
- https://en.wikipedia.org/wiki/X86
- https://en.wikipedia.org/wiki/IA-32
- https://en.wikipedia.org/wiki/X86-64
Node.js proposal - os.sysarch()
Note: There is
a proposal
to add this functionality to Node.js as os.sysarch().
license
MIT. Copyright (c) Feross Aboukhadijeh.