Migration

BumbleVue 1.0 is a fork of PrimeVue v4.5 following the announcement by PrimeTek to convert to a closed-source and dual-license model. The goal of BumbleVue is to provide a free and open-source alternative to PrimeVue v4, while maintaining compatibility with existing PrimeVue v4 applications. That said, since there was a rebrand, there are still some changes that need to be made to migrate from PrimeVue v4 to BumbleVue 1.0. There are also some things related to the larger Prime* ecosystem that have not been adopted into the BumbleVue ecosystem. This guide will help you with the migration process and highlight the differences between the two libraries.

TypeScript Generics Support

The types for 32 components have been updated to add generic types inferred from the component's props, replacing many uses of the any type. This change improves type safety and allows for better type inference when using these components in TypeScript projects. If you are using TypeScript, you may see some new type errors if your code was not consistent with the expected types of these components.

Package Renames

The following packages have been renamed to reflect the new branding of BumbleVue:

Export / Variable Renames

In addition to renamed packages, some exports and variables have been renamed to reflect the new branding of BumbleVue. This includes but is not limited to the following:

• usePrimeVue renamed to useBumbleVue
• $primevue global property renamed to $bumblevue
• PrimeVueConfiguration renamed to BumbleVueConfiguration

In general the renames are fairly obvious replacements of PrimeVue with BumbleVue.

Note that the prefix "p-" and style class "pi" for PrimeIcons remains the same for BumbleIcons.

Dropped packages/features/ecosystem products

In order to focus on the core BumbleVue project and maintain it as free and open source, some of the features and ecosystem products from PrimeTek have no alternative in BumbleVue.

LLM / MCP

AI has largely been destructive to the economy, environment, and workforce. It has played no small part in PrimeTek's decision to go closed-source and pursue more aggressive monetization. Finally, there are emerging studies, and self-testimonies showing a cognitive decline in people that rely on AI. It is recognized that using AI as a tool, rather than replacing skilled developers and real human cognition, has a place in the future of software development, but the use of "agentic" AI is not something that will be supported at this point in time. If you want to use AI like this, I fully support forks of the PrimeVue LLM/MCP packages for that purpose, but for now there will be no support for it in BumbleVue.

Volt UI

While an interesting project, there is no alternative currently in BumbleVue yet. Although a rebranded version of Volt UI has not been ruled out for the future, it is not a priority at this time.

PrimeFlex

This project was already deprecated and has not been migrated into the BumbleVue ecosystem as it has no place when better solutions like TailwindCSS exist.

PrimeBlocks / Templates

The are no plans currently for selling templates or "UI blocks". In 2025, Tailwind announced they had to downsize by 75% and placed the blame solely on AI. The fact is that monetizing something than can easily be replicated by AI, or even a skilled designer, is not a sustainable business model and this is not a desired route for monetization of BumbleVue or even a desired free offering.

PrimeCLT

Not essential.