Hello,
Is anyone using Xero? Please give us some feedback.
How can it be useful for UNA? The Xero description page here in UNA doesn't make it clear enough.
Thanks
UNA 14RC3 -cloud hosted by UNA - all mods updated.
Concerning the UNA core invitations module @LeonidS and the 'invite by email' in the great affiliate module by @AQB Soft
Can anyone confirm? Right now anybody can sent an invitation to any email adress. No matter if this email adress is already registered or this email adresses already got an invitation and is in some kind of 'pending' status. Is that how it should work?
- A) and D) User can send invitation to the own email adress
- B) and C) Users can send invitation to already registered emails, the admin in this case
An Additional Question to both UNA invitations & AQB Affiliates : Where can a member manage the invitations he has sent? At least the ability to see a list of email addresses an invitation was sent to?
I think I remember in older UNA versions there was a message when sending an invitation to an already sent or already registered email adress.....hm, was it like that?
( imagine using the points system or any other one to reward users by sending invitations... a real mess ;)
The Coozila! 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 Coozila?
- 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, Coozila! 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 Nginx Instances: Optimized for web traffic management.
- 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.
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.
If you would like to proceed with this option, please contact us via email first, as this package only includes the basic version with 2 router and 2 DragonflyDB instances 1 master and 1 slave. For more advanced configurations, please contact us via email for a tailored offer.
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
- Coozila!: 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 Coozila! repository:
Installation Assistance
If you would like assistance with the installation of this product, please contact Coozila! Labs at labs@coozila.com. Our team is ready 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.
You can also check out the official Coozila! Labs page for more information: Coozila! Labs.
For any inquiries, feel free to reach out through our contact page: Contact Coozila!.
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. Coozila! 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.
One quick question... Over the years, I have seen kind members of this forum offer to "give back" and allow other sites to use their Jitsi servers. Is this really possible or practical? It seems like some of the UNA / Jitsi integrations could be "broken" from one url to another.... Settings, memberships, events, etc.
Surely, these kind individuals were talking about more than just testing their new Jitsi servers. Right?
So. Please confirm that more than one UNA site (sites and urls which I control) can access both features (jitsi meet and video transcoding) on a SINGLE external server. IF I control both servers and have them properly configured in the settings and in the inc/header.inc.php file.
In other words, I have TWO UNA sites on one server which I want to use with ONE remote (unmanaged) server for these two purposes. The two purposes which are not possible on a shared hosting plan. Due to resource constraints.
Thank YOU.
- 678
The Coozila! 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 Coozila?
- 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, Coozila! 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 Nginx Instances: Optimized for web traffic management.
- One 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.
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.
If you would like to proceed with this option, please contact us via email first, as this package only includes the basic version with 2 router and 4 DragonflyDB instances 3 masters and 2 slaves. For more advanced configurations, please contact us via email for a tailored offer.
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
- Coozila!: 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 Coozila! repository:
Installation Assistance
If you would like assistance with the installation of this product, please contact Coozila! Labs at labs@coozila.com. Our team is ready 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.
You can also check out the official Coozila! Labs page for more information: Coozila! Labs.
For any inquiries, feel free to reach out through our contact page: Contact Coozila!.
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. Coozila! 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.
Although the framework is well-structured, there are still numerous areas that require improvement before it can serve as a solid foundation for building a site. At this point, I don’t feel confident enough to utilize it for building a website i just play
For example, when performing a simple search on UNA for the keyword "UNA," you’ll notice many results, and the way these search results are displayed seems disorganized, resembling a mixed salad. The problem is that you cannot edit the page blocks from the search results, which should have backgrounds and padding. Instead, they are all mixed together in a single block, making it difficult to customize individual elements.
Additionally, the search results exhibit inconsistencies in spacing. Some blocks have larger spacing, while others are merged together. Furthermore, it appears that the HTML blocks in the search results lack options to enable or disable backgrounds and padding, contributing to the overall mixed salad effect.
Question for developers: Don't you think the search results page is important? Is that why it has been neglected? I personally think it is the most viewed page after the home page. But I think every developer would like to customize how search results are displayed and how many items in each page block.