Add new...
I would like to report an issue I encountered while integrating Xero services into my application. I am experiencing the following deprecation warning and errors:
Deprecated: http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /opt/una/modules/boonex/xero/plugins/league/oauth2-client/src/Tool/QueryBuilderTrait.php on line 31
Warning: Cannot modify header information - headers already sent by (output started at /opt/una/modules/boonex/xero/plugins/league/oauth2-client/src/Tool/QueryBuilderTrait.php:31) in /opt/una/inc/classes/BxDolTemplate.php on line 3740
Warning: Cannot modify header information - headers already sent by (output started at /opt/una/modules/boonex/xero/plugins/league/oauth2-client/src/Tool/QueryBuilderTrait.php:31) in /opt/una/inc/classes/BxDolTemplate.php on line 3743
Steps to Reproduce:
UNA 14.0.0-RC4, Xero 13.0.2, OAuth2 Server 14.0.1 by UNA INC with PHP 8.1
1. Integrate the Xero service
2. Attempt to AUTORIZE the application
Expected Result:
The application should connect to Xero without any warnings or errors.
Actual Result:
The application throws a deprecation warning related to the `http_build_query()` function and subsequent header modification errors.
Suggested Fix:
It appears that the issue may stem from passing a null value as a prefix to the `http_build_query()` function in the `QueryBuilderTrait.php` file. I suggest ensuring that a valid string is passed as the second parameter to avoid this deprecation warning.
Please let me know if there are any updates regarding this issue or if further information is needed from my side.
Chrome developer:
Page layout may be unexpected due to Quirks Mode
One or more documents in this page is in Quirks Mode, which will render the affected document(s) with quirks incompatible with the current HTML and CSS specifications.
Quirks Mode exists mostly due to historical reasons. If this is not intentional, you can add or modify the DOCTYPE to be `` to render the page in No Quirks Mode.
Affected Resources
1 element
Document in the DOM treeModeURLdocumentQuirks Mode https://www.exemple.com/studio/module.php?name=bx_xero&page=authorize
Learn more: Document compatibility mode
SERVER SETUP:
PHP:
version = 8.1.32 - OK
allow_url_fopen = On - OK
allow_url_include = Off - OK
magic_quotes_gpc = Off - OK
memory_limit = 32 GB - OK
post_max_size = 2 GB - OK
upload_max_filesize = 2 GB - OK
register_globals = Off - OK
safe_mode = Off - OK
disable_functions - OK
php module: curl = curl - OK
php module: gd = gd - OK
php module: mbstring = mbstring - OK
php module: json = json - OK
php module: fileinfo = fileinfo - OK
php module: zip = zip - OK
php module: openssl = openssl - OK
php module: exif = exif - OK
MySQL:
version = 11.7.2 - OK
Web-server: nginx/1.27.4
rewrite_module - UNDEFINED
OS:
Linux localhost 5.15.0-131-generic #141-Ubuntu SMP Fri Jan 10 21:18:28 UTC 2025 x86_64
Site setup
UNA version = 14.0.0-RC4 - OK
Files and folders permissions - please click here to find out if permissions are correct.
ffmpeg -
ffmpeg version 4.4-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2021 the FFmpeg developers
built with gcc 8 (Debian 8.3.0-6)
configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gmp --enable-libgme --enable-gray --enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libdav1d --enable-libxvid --enable-libzvbi --enable-libzimg
libavutil 56. 70.100 / 56. 70.100
libavcodec 58.134.100 / 58.134.100
libavformat 58. 76.100 / 58. 76.100
libavdevice 58. 13.100 / 58. 13.100
libavfilter 7.110.100 / 7.110.100
libswscale 5. 9.100 / 5. 9.100
libswresample 3. 9.100 / 3. 9.100
libpostproc 55. 9.100 / 55. 9.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...
Use -h to get full help or, even better, run 'man ffmpeg'
if you don't know if output is correct then manual server audit may be required.
Mail sending - click here to send test email
Cron jobs -
no crontab for www-data
if you are unsure if output is correct then manual server audit may be required
Last cron jobs execution - 24 Mar 2025 8:59:01 am
Site optimization
PHP:
PHP accelerator = ZendOPcache - OK
PHP setup = fpm-fcgi - OK
MySQL:
key_buffer_size = 128 MB - OK
max_heap_table_size = 16 MB - OK
tmp_table_size = 16 MB - OK
thread_cache_size = 256 - OK
Web-server:
User-side caching for static content - click here to check it in Google Page Speed
If it is not enabled then please consider implement this optimization, since it improve perceived site speed and save the bandwidth.
To apply this optimization you need to have expires_module - UNDEFINED
Server-side content compression - can be checked manually or in "Page Speed" tool build-in into browser.
If it is not enabled then please consider implement this optimization, since it improve perceived site speed and save the bandwidth.
To apply this optimization you need to have deflate_module - UNDEFINED
UNA:
DB cache = On (Memcache based cache engine) - OK
Pages cache = On (Memcache based cache engine) - OK
Page blocks cache = On (Memcache based cache engine) - OK
Templates Cache = On (Memcache based cache engine) - OK
CSS files cache = On - OK
JS files cache = On - OK
Compression for CSS/JS cache = On - OK
Thank you for your attention to this matter!
Regards,
After a fresh install of 14.0.0-RC4, in the Developer application, the Add New Menu option does not work it shows a loading icon, but the menu is never created, no matter how long I wait. However, adding a menu with navigation builder works correctly.
Issue
Encountered a build error in my setup due to an incompatible type in MainActivity.java:
MainActivity.java:15: error: incompatible types: int cannot be converted to boolean SplashScreen.show
Solution
The issue was resolved by eliminating redundancies in the code. If anyone has alternative solutions, they are welcome to share.
Code Fix
Here’s my working implementation:
package com.una.android;
import android.os.Bundle;
import org.devio.rn.splashscreen.SplashScreen;
import com.facebook.react.ReactActivity;
import com.facebook.react.ReactActivityDelegate;
import com.facebook.react.defaults.DefaultNewArchitectureEntryPoint;
import com.facebook.react.defaults.DefaultReactActivityDelegate;
public class MainActivity extends ReactActivity {
@Override
protected void onCreate(Bundle savedInstanceState) {
// Show Splash Screen on start before calling super.onCreate()
SplashScreen.show(this);
super.onCreate(savedInstanceState);
}
/**
* Returns the name of the main component registered from JavaScript.
* This is used to schedule rendering of the component.
*/
@Override
protected String getMainComponentName() {
return "una";
}
/**
* Returns the instance of the {@link ReactActivityDelegate}. Here we use a utility
* class {@link DefaultReactActivityDelegate} which allows you to easily enable Fabric and
* Concurrent React (i.e. React 18) with two boolean flags.
*/
@Override
protected ReactActivityDelegate createReactActivityDelegate() {
return new DefaultReactActivityDelegate(
this,
getMainComponentName(),
// If you opted-in for the New Architecture, we enable the Fabric Renderer.
DefaultNewArchitectureEntryPoint.getFabricEnabled(),
// If you opted-in for the New Architecture, we enable Concurrent React (React 18).
DefaultNewArchitectureEntryPoint.getConcurrentReactEnabled()
);
}
}
Additional Security Exception
Another issue encountered:
java.lang.SecurityException: com.una.android: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts.
Recommended Fix
Modify AndroidManifest.xml to explicitly define the receiver:
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.una.android">
<uses-permission android:name="android.permission.INTERNET" />
<application
android:name=".MainApplication"
android:label="@string/app_name"
android:icon="@mipmap/ic_launcher"
android:allowBackup="false"
android:theme="@style/AppTheme">
<receiver
android:name="com.facebook.react.devsupport.DevSupportReceiver"
android:exported="false" />
<activity
android:name=".MainActivity"
android:label="@string/app_name"
android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|screenSize|smallestScreenSize|uiMode"
android:launchMode="singleTask"
android:windowSoftInputMode="adjustResize"
android:exported="true">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
<intent-filter android:label="UNA.IO">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data
android:scheme="https"
android:host="www.una.io" />
<data
android:scheme="http"
android:host="www.una.io" />
</intent-filter>
</activity>
</application>
</manifest>
Build & Run the App
To apply the changes, clean the build and restart:
cd android ./gradlew clean cd .. npx react-native run-android
Now it seems to work perfectly. More updates coming soon...
I deleted two photos from an album, but the notifications report otherwise. It seems that the developers have mixed up the notifications, as they indicate that images have been added instead of reporting that they were deleted. It's unnecessary to notify friends that something no longer exists; however, the notification could be more useful for the user by indicating that a photo has been removed from the album.
Una 14.0.0-RC3, Albums 14.0.5 by UNA INC
Overview
Our custom offer is entirely tailored to your unique caching requirements. Instead of a fixed configuration, the DragonflyDB cluster will be set up based on your specific needs and workload demands, ensuring optimal performance and scalability.
Flexible DragonflyDB Cluster Configuration
- Tailored Setup: The DragonflyDB cluster will be configured in accordance with your client-specific requirements.
- Scalability: Each DragonflyDB instance supports up to 768 GB of RAM, ensuring that your caching layer can handle high-demand environments with exceptional efficiency.
- Dynamic Resource Allocation: Adjust memory and compute resources as needed, with the flexibility to scale horizontally across multiple servers or cloud environments.
Advanced McRouter Integration
- Intelligent Request Routing: Leverage McRouter’s robust capabilities such as prefix routing, replicated pools, and automated failover to intelligently distribute requests and optimize cache performance.
- Industry-Validated Performance: As highlighted in the Facebook Engineering article, McRouter is engineered to scale Memcached deployments efficiently, ensuring low latency and high reliability.
Licenses
- DragonflyDB Cluster: MIT License
- DragonflyDB: DragonflyDB License
- McRouter: McRouter License
- Memcached: Memcached License
Important Notice Regarding DragonflyDB Usage
In compliance with the Dragonfly Business Source License 1.1 (BSL 1.1):
- Permitted Use: This project involves installing and configuring DragonflyDB as part of your private caching infrastructure.
- Prohibited Use: You cannot offer DragonflyDB as a hosted or managed service, nor provide any solution that allows third parties (other than your employees or contractors) to access or use DragonflyDB features.
This ensures that the service fully respects the licensing terms of DragonflyDB.
Custom Installation Assistance
Our team will work closely with you to deploy a custom configuration that meets your project’s exact specifications. After purchase, please provide:
- Server login credentials
- An SSH key for secure access
- Project details and integration requirements
Please note that we do not offer future support for any implementation solution; this offer does not include a managed service if you require a managed solution, please contact the Dragonfly team.
Key Advantages
- Tailored Configuration: Fully adaptable setup based on your individual needs no preset configurations.
- High Performance & Scalability: Benefit from a solution designed to deliver cutting-edge performance with each DragonflyDB instance supporting up to 768 GB of RAM.
- Advanced Routing: Utilize McRouter’s advanced routing features for intelligent, scalable caching operations.
- Seamless Integration: Our custom offer ensures that your caching infrastructure evolves with your business requirements.
Pricing Note
The displayed price is indicative and represents the minimum for a custom request; it will be personalized based on your project's specific requirements.
For further details or to request a custom pricing quote, please contact me at olariu_romeo@yahoo.it
App Store - More Products: When viewing a product in the app store, the same product is displayed under the “More Products” section, which should instead show other products from the same vendor. The “More Products” section must exclude the currently viewed product from the list; otherwise, it doesn’t serve its purpose. It should only display the other products available, not the one that is currently being viewed.
This visualization error is noticeable and obvious only to those who have few products or just one. On my product pages, I only have three products, so it becomes quite apparent. This issue is also evident for other vendors who have only two or three products. For those with just one product, this HTML block should not be displayed, as it does not make sense to show the same product when there are no other products available.
Does not generate an error in the true sense of the word, but the display does not make sense. Instead, an html block with related products would be more useful for the end user.
The Package for Memcached Cluster integrates DragonflyDB and McRouter, offering a state-of-the-art caching solution tailored for modern applications. This package is designed to maximize scalability and performance, enabling developers to deploy distributed caching layers effortlessly, reduce database load, and significantly improve response times.
Why Choose DragonflyDB Cluster - Basic 2x1x1?
- Simplified Scalability: Deploy a highly efficient distributed caching layer with pre-configured Docker packages, reducing complexity and ensuring faster response times.
- Intelligent Request Routing: Utilize McRouter’s advanced features, such as prefix routing, replicated pools, and failover mechanisms, for seamless cache operation.
- Blazing-Fast Performance: Built on DragonflyDB, delivers a high-speed, fault-tolerant caching system optimized for high-demand environments.
- Dynamic Configuration: Manage and scale your caching infrastructure with live updates, ensuring zero downtime.
- Multi-Level Caching: Implement tiered caching for enhanced data retrieval efficiency.
Core Features
- Optimized Caching: Route requests efficiently across multiple Memcached servers using McRouter for better load balancing and resource management.
- Advanced Routing Logic: Configure routing policies based on prefixes, clusters, or custom requirements using McRouter’s modular routing handles.
- Rich Monitoring Tools: Access detailed statistics and debugging tools for complete visibility into cache performance.
- Security First: Protect data in transit with SSL support and IPv6 compatibility.
- Multi-Threaded Architecture: Leverage multi-core systems for efficient request handling.
Easy Deployment
This package includes pre-configured Docker containers and a straightforward setup process, enabling developers to quickly build a scalable, reliable caching infrastructure.
Included in Your Offer
- One or Two Nginx Instances: Optimized for web traffic management. (We can add an additional instance of NGINX if you already have a Reverse Proxy or a Load Balancer)
- One PHP Instances: Pre-configured for Memcached integration.
- Two McRouter Instances: Intelligent request routing for optimal caching
- Two DragonFlyDB Memcached Instances: Integrated with your existing database and website. One master and one slave
Note: Each “server” refers to one Docker container. All containers can run on the same physical machine or in the cloud for performance and redundancy.
Recommended Server Specifications
For the Cluster configuration, we recommend using a cloud server instance with the following specifications:
- Minimum RAM: 8 GB (This is the minimum requirement to run the cluster effectively for production.) We have tested the application with 4 GB of RAM, and it functions perfectly, as Docker consumes very little memory. However, to achieve maximum speed, the application requires this amount of RAM, which also depends on the quantity of cache on your server. If the RAM fills up quickly, the application’s performance will degrade rapidly, as it runs solely in RAM.
- The data is saved both on disk, and a snapshot of the program data is created. If your server has less memory, only a single instance of DragonflyDB can be run. However, in this case, the cluster loses its significance. A single instance of DragonflyDB requires a minimum of 4 GB of RAM to run effectively.
- Maximum RAM Supported: Each DragonflyDB instance can support up to 768 GB of RAM, enabling extensive caching capabilities. With 4 instances configured, the total RAM available will be 1536 GB. However, in a mirrored setup (replication), the effective storage capacity is halved, resulting in 758 GB of usable RAM. This configuration is cost-effective and suitable for applications with light to moderate traffic.
The DragonflyDB Cluster project is paving the way for a new generation of caching systems, delivering exceptional performance and scalability. Designed to handle demanding workloads, this advanced configuration makes it an ideal choice for large-scale applications.
The application can set a limit on the RAM that can be used. If you have unlimited memory, you can set it to manage automatically, and DragonflyDB will manage its memory based on the available memory on the server.
However, a custom cluster can be configured without limitations and can be horizontally scaled across different geographical areas or within the same data center based on your preferences. For more advanced options, this custom cluster can run in a Multi-Cloud, Multi-Cluster Kubernetes Orchestration setup with Karmada across multiple data centers and with various cloud providers globally, without any limitations.
Key Advantages
- Unparalleled Speed: With performance that can reach up to 25x faster than traditional Memcached, DragonflyDB Cluster is designed for use cases where speed is critical.
- Scalability: The cluster’s advanced architecture supports scaling up to 4.6 TB, offering exceptional capacity for handling massive datasets.
- Flexibility: Adaptable to a wide range of scenarios, users can customize configurations to optimize for their specific requirements.
Handle with Care: Development Status
As a project still under development, the DragonflyDB Cluster team advises users to:
- Test thoroughly in controlled environments before production deployment.
- Adjust configurations to match individual use cases for optimal results.
- Verify licenses to ensure compliance with all third-party dependencies and integrations.
Licenses
- DragonflyDB Cluster: MIT License
- DragonflyDB: DragonflyDB License
- McRouter: McRouter License
- Memcached: Memcached License
Important Notice Regarding DragonflyDB Usage
In compliance with the Dragonfly Business Source License 1.1 (BSL 1.1):
- Permitted Use: This project involves installing and configuring DragonflyDB as part of your private caching infrastructure.
- Prohibited Use: You cannot offer DragonflyDB as a hosted or managed service, nor provide any solution that allows third parties (other than your employees or contractors) to access or use DragonflyDB features.
- One-Time Installation: You can only order a one-time installation for a managed solution. You need to contact the DragonflyDB team to ensure that the service fully respects the licensing terms of DragonflyDB, or you can manage it yourself.
Explore and Contribute
Learn more and become part of the journey by visiting the DragonflyDB Cluster repository on GitHub
Multiple Configurations for Diverse Needs
DragonflyDB Cluster provides several configurations to suit a variety of use cases:
- Basic setup: for smaller-scale applications or testing environments.
- Advanced setup: featuring three routers, three master nodes, and three slave nodes, optimized for performance, fault tolerance, and high availability. If you have a minimum of three servers available for caching, we can install a package on each of them. Each server will have one router and two instances: one DragonflyDB master and one DragonflyDB slave. Additionally, we will set up three Nginx proxy servers in front, along with a load balancer.
- For high availability (HA), a total of six instances are required, which means you will need a minimum of six servers, each with one instance of DragonflyDB. In this case, you will have three master nodes and three slave nodes operating in a mirrored setup, so the available memory will be effectively halved.
Preconfigured packages:
For preconfigured basic packages, you can find them on the app store:
- DragonflyDB Cluster - Basic 2x1x1: Starting from 4GB - 768 GB of usable RAM
- DragonflyDB Cluster - Advance 2x2x2: Starting from 8GB - 1536 GB of usable RAM
- DragonflyDB Cluster - High Availability (HA) 3X3X3: Starting from 8GB - 1536 GB of usable RAM with cold storage failover, reverse proxy and load balancer optimized for high traffic
Please note that we do not offer future support for any implementation solution; this offer does not include a managed service if you require a managed solution, please contact the Dragonfly team.
Custom Installation Assistance
If you would like custom installation of this product, please contact Romulus at olariu_romeo@yahoo.it . I will be happy to help you with the installation process and ensure a smooth setup.
- Based on the size and complexity of your project, we will provide you with a tailored pricing quote.
- For purchasing a custom installation service, please visit the following link: DragonflyDB Cluster -Custom
After Purchase Notes
After your purchase, please provide the following information via email:
- Server login credentials
- An SSH key for secure access
- Details about the project you wish to integrate
Additional Documentation
For more details, please refer to the main repository:
Disclaimer
This product is provided "as is," without any guarantees or warranties regarding its functionality, performance, or reliability. By using this product, you acknowledge that you do so at your own risk. Romulus and its contributors are not liable for any issues, damages, or losses that may arise from the use of this product. We recommend thoroughly testing the product in your own environment before deploying it in a production setting.
APP Diagram:
The Package for Memcached Cluster integrates DragonflyDB and McRouter, offering a state-of-the-art caching solution tailored for modern applications. This package is designed to maximize scalability and performance, enabling developers to deploy distributed caching layers effortlessly, reduce database load, and significantly improve response times.
Why Choose DragonflyDB Cluster?
- Simplified Scalability: Deploy a highly efficient distributed caching layer with pre-configured Docker packages, reducing complexity and ensuring faster response times.
- Intelligent Request Routing: Utilize McRouter’s advanced features, such as prefix routing, replicated pools, and failover mechanisms, for seamless cache operation.
- Blazing-Fast Performance: Built on DragonflyDB, delivers a high-speed, fault-tolerant caching system optimized for high-demand environments.
- Dynamic Configuration: Manage and scale your caching infrastructure with live updates, ensuring zero downtime.
- Multi-Level Caching: Implement tiered caching for enhanced data retrieval efficiency.
Core Features
- Optimized Caching: Route requests efficiently across multiple Memcached servers using McRouter for better load balancing and resource management.
- Advanced Routing Logic: Configure routing policies based on prefixes, clusters, or custom requirements using McRouter’s modular routing handles.
- Rich Monitoring Tools: Access detailed statistics and debugging tools for complete visibility into cache performance.
- Security First: Protect data in transit with SSL support and IPv6 compatibility.
- Multi-Threaded Architecture: Leverage multi-core systems for efficient request handling.
Easy Deployment
This package includes pre-configured Docker containers and a straightforward setup process, enabling developers to quickly build a scalable, reliable caching infrastructure.
Included in Your Offer
- One Caddy Instance: Configured as reverse proxy
- One Nginx Instances: Optimized proxy.
- One or morre PHP Instances: Pre-configured for Memcached integration.
- Two McRouter Instances: Intelligent request routing for optimal caching.
- Four DragonFlyDB Memcached Instances: Integrated with your existing database and website. Two masters and two slaves
Note: Each “server” refers to one Docker container. All containers can run on the same physical machine or in the cloud for performance and redundancy.
Recommended Server Specifications
For the Cluster configuration, we recommend using a cloud server instance with the following specifications:
- Minimum RAM: 16 GB (This is the minimum requirement to run the cluster effectively for production.) We have tested the application with 8 GB of RAM, and it functions perfectly, as Docker consumes very little memory. However, to achieve maximum speed, the application requires this amount of RAM, which also depends on the quantity of cache on your server. If the RAM fills up quickly, the application’s performance will degrade rapidly, as it runs solely in RAM.
- The data is saved both on disk, and a snapshot of the program data is created. If your server has less memory, only a single instance of DragonflyDB can be run. However, in this case, the cluster loses its significance. A single instance of DragonflyDB requires a minimum of 4 GB of RAM to run effectively.
- Maximum RAM Supported: Each DragonflyDB instance can support up to 768 GB of RAM, enabling extensive caching capabilities. With 4 instances configured, the total RAM available will be 3072 GB. However, in a mirrored setup (replication), the effective storage capacity is halved, resulting in 1536 GB of usable RAM. This configuration is cost-effective and suitable for applications with light to moderate traffic.
The DragonflyDB Cluster project is paving the way for a new generation of caching systems, delivering exceptional performance and scalability. Designed to handle demanding workloads, this advanced configuration makes it an ideal choice for large-scale applications.
The application can set a limit on the RAM that can be used. If you have unlimited memory, you can set it to manage automatically, and DragonflyDB will manage its memory based on the available memory on the server.
However, a custom cluster can be configured without limitations and can be horizontally scaled across different geographical areas or within the same data center based on your preferences. For more advanced options, this custom cluster can run in a Multi-Cloud, Multi-Cluster Kubernetes Orchestration setup with Karmada across multiple data centers and with various cloud providers globally, without any limitations.
Key Advantages
- Unparalleled Speed: With performance that can reach up to 25x faster than traditional Memcached, DragonflyDB Cluster is designed for use cases where speed is critical.
- Scalability: The cluster’s advanced architecture supports scaling up to 4.6 TB, offering exceptional capacity for handling massive datasets.
- Flexibility: Adaptable to a wide range of scenarios, users can customize configurations to optimize for their specific requirements.
Handle with Care: Development Status
As a project still under development, the DragonflyDB Cluster team advises users to:
- Test thoroughly in controlled environments before production deployment.
- Adjust configurations to match individual use cases for optimal results.
- Verify licenses to ensure compliance with all third-party dependencies and integrations.
Licenses
- DragonflyDB Cluster: MIT License
- DragonflyDB: DragonflyDB License
- McRouter: McRouter License
- Memcached: Memcached License
Important Notice Regarding DragonflyDB Usage
In compliance with the Dragonfly Business Source License 1.1 (BSL 1.1):
- Permitted Use: This project involves installing and configuring DragonflyDB as part of your private caching infrastructure.
- Prohibited Use: You cannot offer DragonflyDB as a hosted or managed service, nor provide any solution that allows third parties (other than your employees or contractors) to access or use DragonflyDB features.
- One-Time Installation: You can only order a one-time installation for a managed solution. You need to contact the DragonflyDB team to ensure that the service fully respects the licensing terms of DragonflyDB, or you can manage it yourself.
Explore and Contribute
Learn more and become part of the journey by visiting the DragonflyDB Cluster repository on GitHub
Multiple Configurations for Diverse Needs
DragonflyDB Cluster provides several configurations to suit a variety of use cases:
- Basic setup: for smaller-scale applications or testing environments.
- Advanced setup: featuring three routers, three master nodes, and three slave nodes, optimized for performance, fault tolerance, and high availability. If you have a minimum of three servers available for caching, we can install a package on each of them. Each server will have one router and two instances: one DragonflyDB master and one DragonflyDB slave. Additionally, we will set up three Nginx proxy servers in front, along with a load balancer.
- For high availability (HA), a total of six instances are required, which means you will need a minimum of six servers, each with one instance of DragonflyDB. In this case, you will have three master nodes and three slave nodes operating in a mirrored setup, so the available memory will be effectively halved.
Preconfigured packages:
For preconfigured basic packages, you can find them on the app store:
- DragonflyDB Cluster - Basic 2x1x1: Starting from 4GB - 768 GB of usable RAM
- DragonflyDB Cluster - Advance 2x2x2: Starting from 8GB - 1536 GB of usable RAM
- DragonflyDB Cluster - High Availability (HA) 3X3X3: Starting from 8GB - 1536 GB of usable RAM with cold storage failover, reverse proxy and load balancer optimized for high traffic
Please note that we do not offer future support for any implementation solution; this offer does not include a managed service if you require a managed solution, please contact the Dragonfly team.
Custom Installation Assistance
If you would like custom installation of this product, please contact Romulus at olariu_romeo@yahoo.it . I will be happy to help you with the installation process and ensure a smooth setup.
- Based on the size and complexity of your project, we will provide you with a tailored pricing quote.
- For purchasing a custom installation service, please visit the following link: DragonflyDB Cluster -Custom
After Purchase Notes
After your purchase, please provide the following information via email:
- Server login credentials
- An SSH key for secure access
- Details about the project you wish to integrate
Additional Documentation
For more details, please refer to the main repository:
Disclaimer
This product is provided "as is," without any guarantees or warranties regarding its functionality, performance, or reliability. By using this product, you acknowledge that you do so at your own risk. Romulus and its contributors are not liable for any issues, damages, or losses that may arise from the use of this product. We recommend thoroughly testing the product in your own environment before deploying it in a production setting.
What version of Node.js version is required for developing UNA Android and IOS apps with React Native? I have tried all the LTS versions from 16 to 18, 20, 22 and I’m encountering dependency conflicts with each. What is the exact recommended version to avoid these issues? It also seems that this application has not been updated at all for 8 months.
lts version 18
asdf local nodejs 18.18.0
npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-aria/tabs@3.0.0-alpha.2
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-aria/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs
npm WARN @react-aria/tabs@"3.0.0-alpha.2" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-aria/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs
npm WARN @react-aria/tabs@"3.0.0-alpha.2" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/tabs@3.0.0-alpha.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.1" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.1" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-types/tabs@3.0.0-alpha.2
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-types/tabs
npm WARN @react-types/tabs@"3.0.0-alpha.2" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN 3 more (@react-aria/tabs, @react-stately/tabs, @react-stately/tabs)
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-types/tabs
npm WARN @react-types/tabs@"3.0.0-alpha.2" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN 3 more (@react-aria/tabs, @react-stately/tabs, @react-stately/tabs)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/checkbox@3.0.3
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/checkbox@3.0.3
npm WARN node_modules/native-base/node_modules/@react-stately/checkbox
npm WARN @react-stately/checkbox@"3.0.3" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/checkbox@3.0.3
npm WARN node_modules/native-base/node_modules/@react-stately/checkbox
npm WARN @react-stately/checkbox@"3.0.3" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/collections@3.3.0
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/collections@3.3.0
npm WARN node_modules/native-base/node_modules/@react-stately/collections
npm WARN @react-stately/collections@"3.3.0" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/collections@3.3.0
npm WARN node_modules/native-base/node_modules/@react-stately/collections
npm WARN @react-stately/collections@"3.3.0" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/combobox@3.0.0-alpha.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox
npm WARN @react-stately/combobox@"3.0.0-alpha.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox
npm WARN @react-stately/combobox@"3.0.0-alpha.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/radio@3.2.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/radio@3.2.1
npm WARN node_modules/native-base/node_modules/@react-stately/radio
npm WARN @react-stately/radio@"3.2.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/radio@3.2.1
npm WARN node_modules/native-base/node_modules/@react-stately/radio
npm WARN @react-stately/radio@"3.2.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/slider@3.0.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/slider@3.0.1
npm WARN node_modules/native-base/node_modules/@react-stately/slider
npm WARN @react-stately/slider@"3.0.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/slider@3.0.1
npm WARN node_modules/native-base/node_modules/@react-stately/slider
npm WARN @react-stately/slider@"3.0.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/tabs@3.0.0-alpha.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/toggle@3.2.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/toggle@3.2.1
npm WARN node_modules/native-base/node_modules/@react-stately/toggle
npm WARN @react-stately/toggle@"3.2.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/toggle@3.2.1
npm WARN node_modules/native-base/node_modules/@react-stately/toggle
npm WARN @react-stately/toggle@"3.2.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/tabs@3.0.0-alpha.0
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.0
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.0" from @react-aria/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.0
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.0" from @react-aria/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-types/combobox@3.0.0-alpha.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox/node_modules/@react-types/combobox
npm WARN @react-types/combobox@"3.0.0-alpha.1" from @react-stately/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox/node_modules/@react-types/combobox
npm WARN @react-types/combobox@"3.0.0-alpha.1" from @react-stately/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-types/tabs@3.0.0-alpha.2
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/tabs@3.0.0-alpha.2
npm WARN node_modules/native-base/node_modules/@react-stately/tabs/node_modules/@react-types/tabs
npm WARN @react-types/tabs@"3.0.0-alpha.2" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/tabs
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/tabs@3.0.0-alpha.2
npm WARN node_modules/native-base/node_modules/@react-stately/tabs/node_modules/@react-types/tabs
npm WARN @react-types/tabs@"3.0.0-alpha.2" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/tabs
npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
added 1214 packages, and audited 1215 packages in 55s
149 packages are looking for funding
run `npm fund` for details
28 vulnerabilities (2 low, 8 moderate, 17 high, 1 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
exemple for nodejs 18.0.0 if we follow exactly what is written in the .node version file
npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-aria/tabs@3.0.0-alpha.2
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-aria/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs
npm WARN @react-aria/tabs@"3.0.0-alpha.2" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-aria/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs
npm WARN @react-aria/tabs@"3.0.0-alpha.2" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/tabs@3.0.0-alpha.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.1" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.1" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-types/tabs@3.0.0-alpha.2
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-types/tabs
npm WARN @react-types/tabs@"3.0.0-alpha.2" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN 3 more (@react-aria/tabs, @react-stately/tabs, @react-stately/tabs)
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-types/tabs
npm WARN @react-types/tabs@"3.0.0-alpha.2" from @react-native-aria/tabs@0.2.8
npm WARN node_modules/@react-native-aria/tabs
npm WARN 3 more (@react-aria/tabs, @react-stately/tabs, @react-stately/tabs)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/checkbox@3.0.3
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/checkbox@3.0.3
npm WARN node_modules/native-base/node_modules/@react-stately/checkbox
npm WARN @react-stately/checkbox@"3.0.3" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/checkbox@3.0.3
npm WARN node_modules/native-base/node_modules/@react-stately/checkbox
npm WARN @react-stately/checkbox@"3.0.3" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/collections@3.3.0
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/collections@3.3.0
npm WARN node_modules/native-base/node_modules/@react-stately/collections
npm WARN @react-stately/collections@"3.3.0" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/collections@3.3.0
npm WARN node_modules/native-base/node_modules/@react-stately/collections
npm WARN @react-stately/collections@"3.3.0" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/combobox@3.0.0-alpha.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox
npm WARN @react-stately/combobox@"3.0.0-alpha.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox
npm WARN @react-stately/combobox@"3.0.0-alpha.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/radio@3.2.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/radio@3.2.1
npm WARN node_modules/native-base/node_modules/@react-stately/radio
npm WARN @react-stately/radio@"3.2.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/radio@3.2.1
npm WARN node_modules/native-base/node_modules/@react-stately/radio
npm WARN @react-stately/radio@"3.2.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/slider@3.0.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/slider@3.0.1
npm WARN node_modules/native-base/node_modules/@react-stately/slider
npm WARN @react-stately/slider@"3.0.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/slider@3.0.1
npm WARN node_modules/native-base/node_modules/@react-stately/slider
npm WARN @react-stately/slider@"3.0.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/tabs@3.0.0-alpha.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/toggle@3.2.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/toggle@3.2.1
npm WARN node_modules/native-base/node_modules/@react-stately/toggle
npm WARN @react-stately/toggle@"3.2.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/toggle@3.2.1
npm WARN node_modules/native-base/node_modules/@react-stately/toggle
npm WARN @react-stately/toggle@"3.2.1" from native-base@3.4.28
npm WARN node_modules/native-base
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-stately/tabs@3.0.0-alpha.0
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.0
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.0" from @react-aria/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-stately/tabs@3.0.0-alpha.0
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs/node_modules/@react-stately/tabs
npm WARN @react-stately/tabs@"3.0.0-alpha.0" from @react-aria/tabs@3.0.0-alpha.2
npm WARN node_modules/@react-native-aria/tabs/node_modules/@react-aria/tabs
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-types/combobox@3.0.0-alpha.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox/node_modules/@react-types/combobox
npm WARN @react-types/combobox@"3.0.0-alpha.1" from @react-stately/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox/node_modules/@react-types/combobox
npm WARN @react-types/combobox@"3.0.0-alpha.1" from @react-stately/combobox@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/combobox
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @react-types/tabs@3.0.0-alpha.2
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN react@"18.2.0" from the root project
npm WARN 71 more (@react-aria/checkbox, @react-aria/combobox, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/tabs@3.0.0-alpha.2
npm WARN node_modules/native-base/node_modules/@react-stately/tabs/node_modules/@react-types/tabs
npm WARN @react-types/tabs@"3.0.0-alpha.2" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/tabs
npm WARN
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN peer react@"^16.8.0 || ^17.0.0-rc.1" from @react-types/tabs@3.0.0-alpha.2
npm WARN node_modules/native-base/node_modules/@react-stately/tabs/node_modules/@react-types/tabs
npm WARN @react-types/tabs@"3.0.0-alpha.2" from @react-stately/tabs@3.0.0-alpha.1
npm WARN node_modules/native-base/node_modules/@react-stately/tabs
npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
added 1214 packages, and audited 1215 packages in 36s
149 packages are looking for funding
run `npm fund` for details
28 vulnerabilities (2 low, 8 moderate, 17 high, 1 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
Romulus Discussions
