Avoid using readonly for public exposed reactive properties

[frederikprijck]

Changes

Using readonly() kinda changes the types in such a way that it marks all properties as readonly. Instead of actual IdToken (or User) types, it's actualy using an inline type based on the IdToken (but marking everything as readonly).

This means that the Auth0VueClient interface defined properties such as IdTokenClaims as a Ref<IdToken | undefined>, the Auth0VuePlugin has them being inferred to as DeepReadonly<UnwrapNestedRefs<IdToken>>, which doesn't always align.

This can become complicated to type properly, while they don't really need to be marked as read-only.

Dropping the read-only shouldn't cause issues, as they share the same public API:

const x = ref<IdToken>({__raw: 'abc'});
const xReadOnly = readonly(x);

console.log('raw', { x, xReadOnly }); // Logs x: RefImpl and xReadOnly: Proxy(RefImpl)
console.log('value', { x: x.value, xReadOnly: xReadOnly?.value }); // Logs 2x Proxy(Object)
console.log('property', { x: x.value.__raw, xReadOnly: xReadOnly?.value.__raw }); // Logs 2x 'abc'

With our SDK, the above would be:

console.log(auth0.idTokenClaims); // Logs RefImpl after this PR, Proxy(RefImpl) before this PR.
console.log(auth0.idTokenClaims.value); // Logs Proxy(Object) before and after this PR.
console.log(auth0.idTokenClaims.value.name); // Logs the correct claim value before and after this PR

As you can see, this should not change anything in how users can interact with our public reactive API.

References

Closes #240

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All code quality tools/guidelines have been run/followed

[jonasingvar]

I was having this issue with the readonly properties (build would fail) and have confirmed it's working now with this fix. Thank you