Releases: 51Degrees/device-detection-node
Releases · 51Degrees/device-detection-node
Version 4.3.3
- BUILD: Add node 16 to tested versions
- REF: Update jest version
Version 4.3.2
- BUG: Updated binding.51d to pass -latomic command when linking.
Version 4.3.1
Included changes:
- BUILD: Added 'submodule-trigger.yml' pipeline to support automated release process.
- BUILD: Added a step to 'build-and-test.yml' pipeline to auto complete a pull request to main as part of the automated release process.
- BUILD: Changed nightly build to just run tests, not create packages.
- BUG: Cloud request engine now has a mechanism to set the Origin header.
Version 4.3.0
- BUILD: Make build binaries part of CI pipeline.
- BUILD: Improved continuous integration
- FEAT: Added typescript declarations.
- BUILD: Updated dependecy versions.
Version 4.2.3
Included changes:
- REF: Update device-detection-cxx module to support new data file - this prevents a spurious crash in backend when new data file is used.
Releases:
Version 4.2.2
Included changes:
- DOC: Replace www.51degrees.com with 51degrees.com
- BUILD: Fixed warnings generated by C/C++ compilation process and treat all warnings as errors for Windows and MacOS platforms
- FEAT: Property tests for device detection cloud and on-premise
Releases:
Version 4.2.1
Included changes:
- FEAT: Added supports for Node 14.
- DOC: Added readme file for each sub module.
- REF: Updated references to fiftyone.pipeline.* 4.2.1 modules
Releases:
Version 4.2.0
Included Changes:
- FEAT: The underlying C code used for device detection supports caching. There is no benefit to caching results within the Node.js layer implementation, therefore the
cacheandcacheSizebuilder arguments will throw an exception if a cache is added to on-premise engines. The overhead of a having to handle object lifetimes, coupled with the speed of the actual detection being comparable to a cache lookup, means that performance is not improved by adding a cache to on-premise engines. - TEST: Added tests to set cache and verify that the correct exception is thrown. All tests and examples that check caching have been removed.
- OPTIM: Updated the error messages to provide more helpful information.
- TEST: Check that correct error message are returned for each failed scenario.
- EXAMPLE: Added missing on-premise examples:
Match Metrics,Offline Processing,Performance. - TEST: Added tests for each added example.
- EXAMPLE: Updated examples and tests to match the changes to
FlowData. - TEST: Added test to check that appropriate error message is returned when open file that contains bad data.
- TEST: Added performance test for endpoints using Apache Bench.
- FEAT: Added the following options to DeviceDetectionPipelineBuilder: restrictedProperties, updateMatchedUserAgent, maxMatchedUserAgentLength, drift, difference, usePredictiveGraph, usePerformanceGraph.
- OPTIM: Binaries will no longer be held in Git.
- DOC: Readme now details the process to build the binaries. Examples list is also updated together with details of how to run the example using npm packages or directly from the Git repository.
- REORG: Packaging is now restructured to 4 separated modules fiftyone.devicedetection.onpremise, fiftyone.devicedetection.cloud, fiftyone.devicedetection and fiftyone.devicedetection.shared.
- FEAT: Match metrics 'UserAgents' now returns an arrays of matched User-Agents segments.
- TEST: Added tests for corrupted data handling during initialisation.
Releases: