fix: form to accept react component

[chanceaclark]

Reasons for making this change

In development, we weren't able to pass a react component into the tagName prop. This is valid in React but was unable to test in development due to PropTypes.

It also looked like some packages weren't properly locked, so I've updated those.

Side Note: We may want to look into migrating to yarn. Just a 💭

Checklist

• I'm adding or updating code
  • I've added and/or updated tests
  • I've updated docs if needed

[chanceaclark]

I think I should be able to make this just PropTypes.elementType 🤔

[epicfaace]

Hmm, does PropTypes.elementType include strings?

[chanceaclark]

Yeah, it's a ReactComponentLike:

export type ReactComponentLike =
    | string
    | ((props: any, context?: any) => any)
    | (new (props: any, context?: any) => any);

[epicfaace]

Looks good, thanks. I wonder if tagName is now a bit misleading though since it really refers to a component name...

[chanceaclark]

@epicfaace I agree, but if we wanted to change it, it would be a BREAKING CHANGE. I guess since v2 is in alpha it would be fine to add a BC?

And since rjsf is converting to TypeScript, I think it might be more beneficial for development to restrict the prop via typings vs. prop-types.

[epicfaace]

Yeah, true. I'll go ahead and merge this for now, though. Do you have any suggestions for what a better prop name might be?

[chanceaclark]

We could go for the as prop. It's used in some libraries, like styled-components. Material-ui and Atlaskit uses the component prop, which IMO, prefer.