Clear and concise description of the problem

In order to release v1, a parity list spreadsheet needs to be created for internal use. A list comparing the feature set of bv to bvn, including: props, emits, and functionality.

This is vital to the release of the library as we need to be able to properly index what is missing and what is simply removed behavior.

Even things that are declared deprecated in bv should be noted on the parity list, but have a comment describing they are deprecated.

An online spreadsheet (please do not post direct files here, for security) as an evolving spreadsheet.

Suggested solution

An online spreadsheet should be created here to document every components parity with that of bv. It should contain information about prop differences, (say if bv had type "string" and we had type "sm" | 'md' | 'lg'. It's not invalid, but it needs to be documented)

Alternative

This needs to be finished by the time v1 is released

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.